Retry CRD creation in case of conflict #12814
Merged
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.
Proposed Changes
Retry CRD creation in case of conflict
Also cleans up some of the
server.Contextfactory creation stuff to eliminate unused code paths and avoid registering the Helm controller when helm is disabled.As of fe465cc we no longer call
NewContextoutsidepkg/server, so theisServerbool flag to use the supervisor kubeconfig and create an event recorder is unnecessary.Types of Changes
bugfix
tech debt
Verification
See linked issue - this is difficult to reproduce due to tight timing; multiple control-plane nodes need to be at the exact same spot in the startup sequence at the exact same time.
Testing
Linked Issues
User-Facing Change
Further Comments