You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/proposals/20250513-chained-and-efficient-upgrades-for-clusters-with-managed-topologies.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -247,8 +247,11 @@ consistent with `controlPlaneUpgrades` and also compliant with the [Kubernetes v
247
247
- version: v1.31.0
248
248
- version: v1.32.3
249
249
```
250
-
251
-
Please note:
250
+
251
+
Note: in this case the system will take into consideration the provided `workersUpgrades`, and validated it is
252
+
consistent with `controlPlaneUpgrades` and also compliant with the [Kubernetes version skew policy](https://kubernetes.io/releases/version-skew-policy/).
253
+
254
+
Plase also consider that:
252
255
- In case both the list of Kubernetes versions and the runtime extension definition will be left empty in a cluster class,
253
256
Cluster API will behave as of today: only upgrades to the next minor are allowed for the corresponding clusters.
254
257
- If the list of Kubernetes versions is defined in a ClusterClass, the system is going to use this info also in
0 commit comments