🚀 Release v1.12.0-rc.1 #13100
Merged
🚀 Release v1.12.0-rc.1 #13100
+446
−0
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
k8s-ci-robot
added
area/release
k8s-ci-robot
added
the
size/L
aman4433
reviewed
Dec 2, 2025
CHANGELOG/v1.12.0-rc.1.md
Outdated
| - Chained upgrades | ||
| - Clusters using managed topologies can now to upgrade by more than one minor Kubernetes version by performing chained and efficient upgrades. | ||
| - Upgrade plan will be computed using Kubernetes version from the ClusterClass or by calling a new runtimeExtension (also defined in the ClusterClass) | ||
| - Existing lifecycle hooks have been adapted to the new workflow, new lifecycle hooks have been introduced to allo granular control of the upgrade steps. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Existing lifecycle hooks have been adapted to the new workflow, new lifecycle hooks have been introduced to allo granular control of the upgrade steps. | |
| - Existing lifecycle hooks have been adapted to the new workflow, new lifecycle hooks have been introduced to allow granular control of the upgrade steps. |
CHANGELOG/v1.12.0-rc.1.md
Outdated
| - Can be enabled with the new `InPlaceUpdates` feature gate | ||
| - More details can be found in the [proposal](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20240807-in-place-updates.md) | ||
| - Chained upgrades | ||
| - Clusters using managed topologies can now to upgrade by more than one minor Kubernetes version by performing chained and efficient upgrades. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Clusters using managed topologies can now to upgrade by more than one minor Kubernetes version by performing chained and efficient upgrades. | |
| - Clusters using managed topologies can now upgrade by more than one minor Kubernetes version by performing chained and efficient upgrades. |
Signed-off-by: chandankumar4 <[email protected]>
chandankumar4
force-pushed
the
release-notes-v1.12.0-rc.1
branch
from
3ed88c7 to
0cd66c8
Compare
k8s-ci-robot
added
the
lgtm
Contributor
|
LGTM label has been added. Git tree hash: b9cbd7cc8e3967ed8400fb837fb89d4ad63ef22c
|
Member
|
/lgtm |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
Member
|
Note: I have also updated #12771 (comment) with the changes above |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Part of: #12771
/area release