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
\* There is an issue with CRDs in Kubernetes v1.23.{0-2}. ClusterClass with patches is affected by that (for more details please see [this issue](https://github.com/kubernetes-sigs/cluster-api/issues/5990)). Therefore we recommend to use Kubernetes v1.23.3+ with ClusterClass.
80
82
Previous Kubernetes **minor** versions are not affected.
@@ -85,35 +87,37 @@ The Core Provider also talks to API server of every Workload Cluster. Therefore,
The Kubeadm Control Plane Provider talks to the API server and etcd members of every Workload Cluster whose control plane it owns. It uses the etcd v3 API.
119
123
@@ -131,11 +135,17 @@ The Kubeadm Control Plane requires the Kubeadm Bootstrap Provider.
131
135
| v1.1 (v1beta1) | v1.9.3 |
132
136
| v1.2 (v1beta1) | v1.9.3 (v1.10.0 with >= v1.2.7) |
133
137
| v1.3 (v1beta1) | v1.10.0 |
138
+
| v1.4 (v1beta1) | v1.10.0 |
134
139
135
140
#### Kubernetes version specific notes
136
141
137
-
**1.24**:
142
+
**1.26**:
143
+
* No specific notes
138
144
145
+
**1.25**:
146
+
* No specific notes
147
+
148
+
**1.24**:
139
149
* Kubeadm Bootstrap Provider:
140
150
* `kubeadm` now sets both the `node-role.kubernetes.io/control-plane` and `node-role.kubernetes.io/master` taints on control plane nodes.
141
151
* `kubeadm` now only sets the `node-role.kubernetes.io/control-plane` label on control plane nodes (the `node-role.kubernetes.io/master` label is not set anymore).
@@ -144,8 +154,7 @@ The Kubeadm Control Plane requires the Kubeadm Bootstrap Provider.
144
154
145
155
#### clusterctl
146
156
147
-
It is strongly recommended to always use the latest version of [clusterctl](../clusterctl/overview.md), in order to
148
-
get all the fixes/latest changes.
157
+
It is strongly recommended to always use the latest version of [clusterctl](../clusterctl/overview.md), in order to get all the fixes/latest changes.
149
158
150
159
In case of upgrades, clusterctl should be upgraded first and then used to upgrade all the other components.
0 commit comments