Repository navigation
runtime/kubernetes: skip unreachable clusters - #3244
Merged
Merged
Conversation
The GKE build clusters were suspended, and every submission still probed each of them three times before falling back, logging thousands of 403s. Mark a cluster dead for 10 minutes after it fails (no retries on 401/403), skip it while dead, and fall back to the next live cluster if submission fails for a cluster-side reason. Clusters rejoin automatically if they recover, so they can stay in the config. Signed-off-by: Denys Fedoryshchenko <denys.f@collabora.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The GKE build clusters were suspended, and every submission still probed each of them three times before falling back, logging thousands of 403s.
Mark a cluster dead for 10 minutes after it fails (no retries on 401/403), skip it while dead, and fall back to the next live cluster if submission fails for a cluster-side reason. Clusters rejoin automatically if they recover, so they can stay in the config.