-
Notifications
You must be signed in to change notification settings - Fork 50
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
Degraded service when some pods CrashLoop on startup #59
Labels
bug
Something isn't working
Comments
sbidoul
changed the title
Degrade service when some pods CrashLoopback
Degraded service when some pods CrashLoopback
May 9, 2022
This was triggered by OCA/oca-ci#29 |
sbidoul
changed the title
Degraded service when some pods CrashLoopback
Degraded service when some pods CrashLoop on startup
Oct 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When some builds are initialized but fail to start and CrashLoopBackOff, runboat does not correctly account for the number of started builds and let the cluster run out of pods.
To be investigated.
The text was updated successfully, but these errors were encountered: