upgrade to capi v1.11.0 and its v1beta2 api #98
Merged
Conversation
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
schrej
force-pushed
the
capi/1.11
branch
3 times, most recently
from
6b53dec to
422d565
Compare
Collaborator
|
LGTM |
watzkuh
approved these changes
Sep 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Upgrades to the latest Cluster API version 1.11.0 and its new v1beta2 api.
This PR also includes some technically breaking API changes, with semi-severe impact. Since we haven't released a proper version yet, we'll perform these changes without introducing a new api version, to avoid all the hassle of conversion.
[]metav1.Conditioninstead ofclusterv1.Conditionsseverityon conditionslastObservedGenerationfield helps with avoiding stale conditionsdepends on kubernetes-sigs/cluster-api-ipam-provider-in-cluster#349