kubernetes: jitter transient dial retries - #4039
Merged
crazy-max merged 1 commit intoSep 14, 2026
Merged
Conversation
crazy-max
force-pushed
the
kubernetes-dial-backoff-jitter
branch
from
September 2, 2026 13:13
03eccbd to
503d231
Compare
crazy-max
marked this pull request as ready for review
September 2, 2026 13:16
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
kubernetes-dial-backoff-jitter
branch
from
September 2, 2026 13:20
503d231 to
d61e36d
Compare
AkihiroSuda
approved these changes
Sep 2, 2026
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
2 participants
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.
closes #3995
Kubernetes dial retries now add jitter to the exponential backoff used for transient connection errors. This keeps concurrent builders from retrying in lockstep when node readiness gets ahead of CSR approval and many builds hit the same temporary TLS failure at once.
The jitter is additive, so retries never happen sooner than the existing exponential schedule would allow, and the delay remains capped by the configured maximum.