Swap capi CRD race condition patch for CR bump #2916
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.
Description of changes:
The bug has been fixed in controller-runtime so now we don't need to detect the error and restart the pod. This CR bump is already merged in capi 1.6, once the new patch is out in a couple weeks, we can remove this new patch and update capi.
The fix for CR 0.16: kubernetes-sigs/controller-runtime#2677
Improvements related to this issue for CR moving forward (available in future capi 1.7): kubernetes-sigs/controller-runtime#2663
Capi bump: kubernetes-sigs/cluster-api#10132
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.