allocator: crd: jitter identity creation#42282
Merged
squeed merged 1 commit intocilium:mainfrom Nov 10, 2025
Merged
Conversation
giorio94
reviewed
Oct 21, 2025
This adds some jitter to the allocator backoff, as well as waiting a random time before first allocation. This aims to reduce collisions where a duplicate identity is created for the same set of labels. This is only enabled for the CRD allocator, as it can collide when allocating the same identity. The kvstore allocator does not suffer this problem. Signed-off-by: Casey Callendrello <cdc@isovalent.com>
1e0178f to
93cde57
Compare
Contributor
Author
|
/test |
Contributor
Author
|
This was reverted in #43127 |
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
4 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.
This adds some jitter to the allocator backoff, as well as waiting a random time before first allocation. This aims to reduce collisions where a duplicate identity is created for the same set of labels.
This is only enabled for the CRD allocator, as it can collide when allocating the same identity. The kvstore allocator does not suffer this problem.
This works in concert with #38031, which can delay re-allocations for up to 30 seconds. That option protects against overload when a large namespace is re-labeled. This is smaller in scope, with less delay, intended only to reduce duplicates.