📖 Improve v1.12 migration docs #13079
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
size/L
k8s-ci-robot
added
the
cncf-cla: yes
There was a problem hiding this comment.
this is a placeholder, #12971 is going to add the content of this PR
There was a problem hiding this comment.
I see the corresponding PR is merged and it needs a rebase?
|
/test pull-cluster-api-verify-main |
|
/test pull-cluster-api-test-main |
fabriziopandini
force-pushed
the
improve-1.12-migration-docs
branch
from
55882f4 to
df98b9c
Compare
|
/cherry-pick release-1.12 |
|
@fabriziopandini: once the present PR merges, I will cherry-pick it on top of In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
fabriziopandini
force-pushed
the
improve-1.12-migration-docs
branch
from
df98b9c to
5ac7f28
Compare
| - A new, optional rule has been added to the control plane contract, defining what is required for implementing support | ||
| for in-place updates. |
There was a problem hiding this comment.
Changes for the control plane contract are included in #13088
k8s-ci-robot
added
the
needs-rebase
| - The new `spec.taint` field has been added. | ||
| - The `HealthCheckSucceeded` condition reports a new `UnhealthyMachine` reason when `unhealthyMachineConditions` checks fail | ||
| - The `UpToDate` condition reports a new `Updating` reason when a machine is performing in-place updates | ||
| - The new `Updating` condition has been added. It reports status `true` when a machine is performing in-place updates. |
There was a problem hiding this comment.
| - The new `Updating` condition has been added. It reports status `true` when a machine is performing in-place updates. | |
| - The new `Updating` condition has been added. It reports status `True` when a machine is performing in-place updates. |
status in condition is uppercase :-)
|
|
||
| - Lifecycle hooks | ||
| - The request message for the `BeforeClusterUpgrade` hook has been extended to include info about the upgrade plan. | ||
| - The new `BeforeControlPlaneUpgrade` hook has been added; the hook is called before each "upgrade control plane" step; |
There was a problem hiding this comment.
is semicolon (;) intentional?
|
|
||
| ## Deprecation | ||
|
|
||
| - The following reasons for the `TopologyReconciled` condition on the `Cluster`object are now deprecated |
There was a problem hiding this comment.
| - The following reasons for the `TopologyReconciled` condition on the `Cluster`object are now deprecated | |
| - The following reasons for the `TopologyReconciled` condition on the `Cluster` object are now deprecated |
| will implement temporarily compatibility with the deprecated v1beta1 version of the Cluster API contract | ||
| - Compatibility is only intended to ease the transition for providers, and it has some limitations; please | ||
| read details in following paragraphs. | ||
| - Compatibility support for the v1beta1 version of the Cluster API contract will be removed tentatively in August 2026 |
There was a problem hiding this comment.
| - Compatibility support for the v1beta1 version of the Cluster API contract will be removed tentatively in August 2026 | |
| - Compatibility support for the v1beta1 version of the Cluster API contract will be removed tentatively in August 2026. |
fabriziopandini
force-pushed
the
improve-1.12-migration-docs
branch
from
5ac7f28 to
c4bf7e4
Compare
k8s-ci-robot
removed
the
needs-rebase
fabriziopandini
force-pushed
the
improve-1.12-migration-docs
branch
from
c4bf7e4 to
dadcf7d
Compare
fabriziopandini
added
the
tide/merge-method-squash
fabriziopandini
force-pushed
the
improve-1.12-migration-docs
branch
from
dadcf7d to
8fa1a67
Compare
5 participants
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):Fixes #
/area documentation