Skip to content

Commit c4b4c29

Browse files
k8s-ci-robotk8s-ci-robot
authored
Merge pull request #5998 from sbueringer/pr-crd-issue-note
📖 book: Add note about Kubernetes v1.23.{0-2} CRD issue and ClusterClass
2 parents 18c7ec8 + 5b799bb commit c4b4c29

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

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

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## Supported Versions
44

5-
The Cluster API team maintains branches for **v1.0 (v1beta1)** **v0.4 (v1alpha4)** and **v0.3 (v1alpha3)**, the most recent releases.
5+
The Cluster API team maintains branches for **v1.x (v1beta1)** **v0.4 (v1alpha4)** and **v0.3 (v1alpha3)**, the most recent releases.
66

77
Releases include these components:
88

@@ -26,8 +26,8 @@ The Core Provider, Kubeadm Bootstrap Provider, and Kubeadm Control Plane Provide
2626
In some cases, the Management Cluster is separate from the Workload Clusters. The Kubernetes version of the Management and Workload Clusters are allowed to be different.
2727

2828
Management Clusters and Workload Clusters can be upgraded independently and in any order, however, if you are additionally moving from
29-
v1alpha3 (v0.3.x) to v1beta1 (v1.0.x) as part of the upgrade rollout, the management cluster will need to be upgraded to at least v1.19.x,
30-
prior to upgrading any workload cluster using Cluster API v1beta1 (v1.0.x)
29+
v1alpha3 (v0.3.x) to v1beta1 (v1.x) as part of the upgrade rollout, the management cluster will need to be upgraded to at least v1.19.x,
30+
prior to upgrading any workload cluster using Cluster API v1beta1 (v1.x)
3131

3232
These diagrams show the relationships between components in a Cluster API release (yellow), and other components (white).
3333

@@ -43,7 +43,7 @@ These diagrams show the relationships between components in a Cluster API releas
4343

4444
#### Core Provider (`cluster-api-controller`)
4545

46-
| | CAPI v1alpha3 (v0.3) Management | CAPI v1alpha3 (v0.3) Workload | CAPI v1alpha4 (v0.4) Management | CAPI v1alpha4 (v0.4) Workload | CAPI v1beta1 (v1.0) Management | CAPI v1beta1 (v1.0) Workload |
46+
| | CAPI v1alpha3 (v0.3) Management | CAPI v1alpha3 (v0.3) Workload | CAPI v1alpha4 (v0.4) Management | CAPI v1alpha4 (v0.4) Workload | CAPI v1beta1 (v1.x) Management | CAPI v1beta1 (v1.x) Workload |
4747
| ---------------- | -------------------------------- | ----------------------------- | -------------------------------- | ----------------------------- | -------------------------------- | ----------------------------- |
4848
| Kubernetes v1.16 | ✓ | ✓ | | | | |
4949
| Kubernetes v1.17 | ✓ | ✓ | | | | |
@@ -52,13 +52,16 @@ These diagrams show the relationships between components in a Cluster API releas
5252
| Kubernetes v1.20 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
5353
| Kubernetes v1.21 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
5454
| Kubernetes v1.22 | | ✓ | ✓ | ✓ | ✓ | ✓ |
55-
| Kubernetes v1.23 | | | ✓ | ✓ | ✓ | ✓ |
55+
| Kubernetes v1.23* | | | ✓ | ✓ | ✓ | ✓ |
56+
57+
\* 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.
58+
Previous Kubernetes **minor** versions are not affected.
5659

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

5962
#### Kubeadm Bootstrap Provider (`kubeadm-bootstrap-controller`)
6063

61-
| | CAPI v1alpha3 (v0.3) Management | CAPI v1alpha3 (v0.3) Workload | CAPI v1alpha4 (v0.4) Management | CAPI v1alpha4 (v0.4) Workload | CAPI v1beta1 (v1.0) Management | CAPI v1beta1 (v1.0) Workload |
64+
| | CAPI v1alpha3 (v0.3) Management | CAPI v1alpha3 (v0.3) Workload | CAPI v1alpha4 (v0.4) Management | CAPI v1alpha4 (v0.4) Workload | CAPI v1beta1 (v1.x) Management | CAPI v1beta1 (v1.x) Workload |
6265
| ---------------------------------- | -------------------------------- | ----------------------------- | ------------------------------- | ----------------------------- | ------------------------------- | ----------------------------- |
6366
| Kubernetes v1.16 + kubeadm/v1beta2 | ✓ | ✓ | | | | |
6467
| Kubernetes v1.17 + kubeadm/v1beta2 | ✓ | ✓ | | | | |
@@ -73,7 +76,7 @@ The Kubeadm Bootstrap Provider generates kubeadm configuration using the API ver
7376

7477
#### Kubeadm Control Plane Provider (`kubeadm-control-plane-controller`)
7578

76-
| | CAPI v1alpha3 (v0.3) Management | CAPI v1alpha3 (v0.3) Workload | CAPI v1alpha4 (v0.4) Management | CAPI v1alpha4 (v0.4) Workload | CAPI v1beta1 (v1.0) Management | CAPI v1beta1 (v1.0) Workload |
79+
| | CAPI v1alpha3 (v0.3) Management | CAPI v1alpha3 (v0.3) Workload | CAPI v1alpha4 (v0.4) Management | CAPI v1alpha4 (v0.4) Workload | CAPI v1beta1 (v1.x) Management | CAPI v1beta1 (v1.x) Workload |
7780
| -------------------------- | ------------------------------- | ----------------------------- | ------------------------------- | ----------------------------- | ------------------------------- | ----------------------------- |
7881
| Kubernetes v1.16 + etcd/v3 | ✓ | ✓ | | | | |
7982
| Kubernetes v1.17 + etcd/v3 | ✓ | ✓ | | | | |

0 commit comments

Comments
 (0)