-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If the cluster is "too slow" zarf init can fail due to the serviceAccount not being created in time #1327
Comments
that is quite the exceptional issue, sounds like your cluster or hardware have significant performance issues, might actually explain some of the other k8s hates jordan things we've been seeing... 🤔 |
We've run 🤦 |
…nuing (#1328) ## Description As the title says. Tbh I'd prefer to actually parse the error or something like that but I don't know how to find the error type that the serviceAccount error is. ## Related Issue Fixes #1327 ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) ## Checklist before merging - [X] Test, docs, adr added or updated as needed - [X] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed ---------
…nuing (#1328) ## Description As the title says. Tbh I'd prefer to actually parse the error or something like that but I don't know how to find the error type that the serviceAccount error is. ## Related Issue Fixes #1327 ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) ## Checklist before merging - [X] Test, docs, adr added or updated as needed - [X] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed ---------
Environment
Device and OS: ubuntu 22.04 epyc based vm
App version: 23.0-rc3
Kubernetes distro being used: kind 1.24.7
Other:
Steps to reproduce
Expected result
Zarf init package deploys successfully regardless of speed of cluster
Actual Result
slow hardware (in this case due to I/O) causes zarf init to fail
Visual Proof (screenshots, videos, text, etc)
The serviceAccount was finished being created 7 seconds after the last retry in my case
Severity/Priority
Medium, just requires running zarf init again
Additional Context
A simple wait between retries should give enough time for a serviceAccount to be created
The text was updated successfully, but these errors were encountered: