Skip to content

Commit 26943ea

Browse files
k8s-ci-robotk8s-ci-robot
authored
Merge pull request #6850 from ykakarap/update-supported-version-1.3
📖 update supported versions for v1.3
2 parents 3015036 + 88fdaed commit 26943ea

File tree

1 file changed

+49
-45
lines changed

1 file changed

+49
-45
lines changed

‎docs/book/src/reference/versions.md

Lines changed: 49 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -20,14 +20,14 @@ the current release (N), N-1, and N-2. Where possible we will go above and beyon
2020
both newer and older versions of Kubernetes:
2121

2222
- For a given Cluster API minor release, we give best-effort support for future Kubernetes versions that are released
23-
during the release's active support period. Depending on the changes made in Kubernetes, users may be required to
24-
update to the next patch release of Cluster API to maintain compatibility.
23+
during the release's active support period. Depending on the changes made in Kubernetes, users may be required to
24+
update to the next patch release of Cluster API to maintain compatibility.
2525
- In some cases where support for future Kubernetes versions can't be added, or is considered not practical or too risky
26-
adding it, the Kubernetes version support matrix for an existing Cluster API minor release will stop at the last supported version.
26+
adding it, the Kubernetes version support matrix for an existing Cluster API minor release will stop at the last supported version.
2727
- Cluster API offers best-effort support for older Kubernetes versions where possible.
28-
Important! this is not a replacement/alternative for upstream Kubernetes support policies!
29-
Support for older version of Kubernetes is limited to "Cluster API can start a Cluster with this Kubernetes version"
30-
and "Cluster API can upgrade to the next Kubernetes version"; it does not include any extended support to Kubernetes itself.
28+
Important! this is not a replacement/alternative for upstream Kubernetes support policies!
29+
Support for older version of Kubernetes is limited to "Cluster API can start a Cluster with this Kubernetes version"
30+
and "Cluster API can upgrade to the next Kubernetes version"; it does not include any extended support to Kubernetes itself.
3131

3232
Whenever a new Cluster API release is cut, we will document the Kubernetes version compatibility matrix the release
3333
has been tested with. Summaries of Kubernetes versions supported by each component are additionally maintained in
@@ -63,77 +63,81 @@ These diagrams show the relationships between components in a Cluster API releas
6363

6464
#### Core Provider (`cluster-api-controller`)
6565

66-
| | CAPI v0.3 (v1alpha3) | CAPI v0.4 (v1alpha4) | CAPI v1.0 (v1beta1) | CAPI v1.1+v1.2 (v1beta1) |
67-
|-------------------|----------------------|----------------------|---------------------|--------------------------|
68-
| Kubernetes v1.16 | ✓ | | | |
69-
| Kubernetes v1.17 | ✓ | | | |
70-
| Kubernetes v1.18 | ✓ | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) |
71-
| Kubernetes v1.19 | ✓ | ✓ | ✓ | ✓ (only workload v1.2) |
72-
| Kubernetes v1.20 | ✓ | ✓ | ✓ | ✓ |
73-
| Kubernetes v1.21 | ✓ | ✓ | ✓ | ✓ |
74-
| Kubernetes v1.22 | ✓ (only workload) | ✓ | ✓ | ✓ |
75-
| Kubernetes v1.23* | | ✓ | ✓ | ✓ |
76-
| Kubernetes v1.24 | | | | ✓ |
66+
| | v0.3 (v1alpha3) | v0.4 (v1alpha4) | v1.0 (v1beta1) | v1.1 (v1beta1) | v1.2 (v1beta1) | v1.3 (v1beta1) |
67+
|-------------------|----------------------|----------------------|---------------------|--------------------|----------------------|---------------------|
68+
| Kubernetes v1.16 | ✓ | | | | | |
69+
| Kubernetes v1.17 | ✓ | | | | | |
70+
| Kubernetes v1.18 | ✓ | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) |
71+
| Kubernetes v1.19 | ✓ | ✓ | ✓ | ✓ | ✓ (only workload) | ✓ (only workload) |
72+
| Kubernetes v1.20 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
73+
| Kubernetes v1.21 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
74+
| Kubernetes v1.22 | ✓ (only workload) | ✓ | ✓ | ✓ | ✓ | ✓ |
75+
| Kubernetes v1.23* | | ✓ | ✓ | ✓ | ✓ | ✓ |
76+
| Kubernetes v1.24 | | | | ✓ | ✓ | ✓ |
7777

7878
\* 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.
79-
Previous Kubernetes **minor** versions are not affected.
80-
\** When using CAPI v1.2 with the CLUSTER_TOPOLOGY experimental feature on, the Kubernetes Version for the management cluster must be >= 1.22.0.
79+
Previous Kubernetes **minor** versions are not affected.
80+
81+
\** When using CAPI v1.2 or v1.3 with the CLUSTER_TOPOLOGY experimental feature on, the Kubernetes Version for the management cluster must be >= 1.22.0.
8182

8283
The Core Provider also talks to API server of every Workload Cluster. Therefore, the Workload Cluster's Kubernetes version must also be compatible.
8384

8485
#### Kubeadm Bootstrap Provider (`kubeadm-bootstrap-controller`)
8586

86-
| | CAPI v0.3 (v1alpha3) | CAPI v0.4 (v1alpha4) | CAPI v1.0 (v1beta1) | CAPI v1.1+v1.2 (v1beta1) |
87-
|-------------------------------------------------------------------|----------------------|----------------------|---------------------|--------------------------|
88-
| Kubernetes v1.16 + kubeadm/v1beta2 | ✓ | | | |
89-
| Kubernetes v1.17 + kubeadm/v1beta2 | ✓ | | | |
90-
| Kubernetes v1.18 + kubeadm/v1beta2 | ✓ | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) |
91-
| Kubernetes v1.19 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ (only workload v1.2) |
92-
| Kubernetes v1.20 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ |
93-
| Kubernetes v1.21 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ |
94-
| Kubernetes v1.22 + kubeadm/v1beta2 (v0.3) kubeadm/v1beta3 (v0.4+) | ✓ (only workload) | ✓ | ✓ | ✓ |
95-
| Kubernetes v1.23 + kubeadm/v1beta3 | | ✓ | ✓ | ✓ |
96-
| Kubernetes v1.24 + kubeadm/v1beta3 | | | | ✓ |
87+
| | v0.3 (v1alpha3) | v0.4 (v1alpha4) | v1.0 (v1beta1) | v1.1 (v1beta1) | v1.2 (v1beta1) | v1.3 (v1beta1) |
88+
|-------------------------------------------------------------------|----------------------|----------------------|---------------------|----------------------|----------------------|--------------------|
89+
| Kubernetes v1.16 + kubeadm/v1beta2 | ✓ | | | | | |
90+
| Kubernetes v1.17 + kubeadm/v1beta2 | ✓ | | | | | |
91+
| Kubernetes v1.18 + kubeadm/v1beta2 | ✓ | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) |
92+
| Kubernetes v1.19 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ | ✓ (only workload) | ✓ (only workload) |
93+
| Kubernetes v1.20 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
94+
| Kubernetes v1.21 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
95+
| Kubernetes v1.22 + kubeadm/v1beta2 (v0.3) kubeadm/v1beta3 (v0.4+) | ✓ (only workload) | ✓ | ✓ | ✓ | ✓ | ✓ |
96+
| Kubernetes v1.23 + kubeadm/v1beta3 | | ✓ | ✓ | ✓ | ✓ | ✓ |
97+
| Kubernetes v1.24 + kubeadm/v1beta3 | | | | ✓ | ✓ | ✓ |
9798

9899
The Kubeadm Bootstrap Provider generates kubeadm configuration using the API version recommended for the target Kubernetes version.
99100

100101
#### Kubeadm Control Plane Provider (`kubeadm-control-plane-controller`)
101102

102-
| | CAPI v0.3 (v1alpha3) | CAPI v0.4 (v1alpha4) | CAPI v1.0 (v1beta1) | CAPI v1.1+v1.2 (v1beta1) |
103-
|----------------------------|----------------------|----------------------|---------------------|--------------------------|
104-
| Kubernetes v1.16 + etcd/v3 | ✓ | | | |
105-
| Kubernetes v1.17 + etcd/v3 | ✓ | | | |
106-
| Kubernetes v1.18 + etcd/v3 | ✓ | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) |
107-
| Kubernetes v1.19 + etcd/v3 | ✓ | ✓ | ✓ | ✓ (only workload v1.2) |
108-
| Kubernetes v1.20 + etcd/v3 | ✓ | ✓ | ✓ | ✓ |
109-
| Kubernetes v1.21 + etcd/v3 | ✓ | ✓ | ✓ | ✓ |
110-
| Kubernetes v1.22 + etcd/v3 | ✓* (only workload) | ✓ | ✓ | ✓ |
111-
| Kubernetes v1.23 + etcd/v3 | | ✓* | ✓* | ✓ |
112-
| Kubernetes v1.24 + etcd/v3 | | | | ✓ |
103+
| | v0.3 (v1alpha3) | v0.4 (v1alpha4) | v1.0 (v1beta1) | v1.1 (v1beta1) | v1.2 (v1beta1) | v1.3 (v1beta1) |
104+
|----------------------------|----------------------|----------------------|---------------------|--------------------|---------------------|---------------------|
105+
| Kubernetes v1.16 + etcd/v3 | ✓ | | | | | |
106+
| Kubernetes v1.17 + etcd/v3 | ✓ | | | | | |
107+
| Kubernetes v1.18 + etcd/v3 | ✓ | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) | ✓ (only workload) |
108+
| Kubernetes v1.19 + etcd/v3 | ✓ | ✓ | ✓ | ✓ | ✓ (only workload) | ✓ (only workload) |
109+
| Kubernetes v1.20 + etcd/v3 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
110+
| Kubernetes v1.21 + etcd/v3 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
111+
| Kubernetes v1.22 + etcd/v3 | ✓* (only workload) | ✓ | ✓ | ✓ | ✓ | ✓ |
112+
| Kubernetes v1.23 + etcd/v3 | | ✓* | ✓* | ✓ | ✓ | ✓ |
113+
| Kubernetes v1.24 + etcd/v3 | | | | ✓ | ✓ | ✓ |
113114

114115
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.
115116

116117
The Kubeadm Control Plane requires the Kubeadm Bootstrap Provider.
117118

118119
\* Newer versions of CoreDNS may not be compatible as an upgrade target for clusters managed with Cluster API. Kubernetes versions marked on the table are supported as an upgrade target only if CoreDNS is not upgraded to the latest version supported by the respective Kubernetes version. The versions supported are represented in the below table.
119120

121+
##### CoreDNS
122+
120123
| CAPI Version | Max CoreDNS Version for Upgrade |
121124
|-----------------|---------------------------------|
122125
| v0.3 (v1alpha3) | v1.8.4 |
123126
| v0.4 (v1alpha4) | v1.8.4 |
124-
| v1.0 (v1beta1) | v1.8.5 |
127+
| v1.0 (v1beta1) | v1.8.5 |
125128
| v1.1 (v1beta1) | v1.9.3 |
126129
| v1.2 (v1beta1) | v1.9.3 |
130+
| v1.3 (v1beta1) | v1.9.3 |
127131

128132
#### Kubernetes version specific notes
129133

130134
**1.24**:
131135

132136
* Kubeadm Bootstrap Provider:
133-
* `kubeadm` now sets both the `node-role.kubernetes.io/control-plane` and `node-role.kubernetes.io/master` taints on control plane nodes.
134-
* `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).
137+
* `kubeadm` now sets both the `node-role.kubernetes.io/control-plane` and `node-role.kubernetes.io/master` taints on control plane nodes.
138+
* `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).
135139
* Kubeadm Bootstrap Provider and Kubeadm Control Plane Provider
136-
* `criSocket` without a scheme prefix has been deprecated in the kubelet since a while. `kubeadm` now shows a warning if no scheme is present and eventually the support for `criSocket`'s without prefix will be dropped. Please adjust the `criSocket` accordingly (e.g. `unix:///var/run/containerd/containerd.sock`) if you are configuring the `criSocket` in CABPK or KCP resources.
140+
* `criSocket` without a scheme prefix has been deprecated in the kubelet since a while. `kubeadm` now shows a warning if no scheme is present and eventually the support for `criSocket`'s without prefix will be dropped. Please adjust the `criSocket` accordingly (e.g. `unix:///var/run/containerd/containerd.sock`) if you are configuring the `criSocket` in CABPK or KCP resources.
137141

138142
#### clusterctl
139143

0 commit comments

Comments
 (0)