Handle resource quota on status forbidden by retrying #4305
+29
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request improves error handling and logging in the
EphemeralRunnerReconcilerfor pod creation failures, particularly distinguishing between invalid and forbidden errors, and adding logic to handle resource quota issues more gracefully.Error handling improvements:
IsInvalidpod creation errors by logging the error and marking theEphemeralRunneras failed, instead of treating it together withIsForbiddenerrors.IsForbiddenerrors by checking if the error is due to resource quota being exceeded. If the quota is exceeded and the runner is about to expire, the ephemeral runner is deleted and recreated; if only the quota is exceeded, the reconcile is retried after 30 seconds. Other forbidden errors fall back to the default handling.Fixes #3629