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/book/src/reference/versions.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,25 +15,25 @@ All Infrastructure Providers are maintained by independent teams. Other Bootstra
15
15
16
16
## Supported Kubernetes Versions
17
17
18
-
The project aims to keep the current minor release compatible with the actively supported Kubernetes minor releases, i.e.,
18
+
The project aims to keep the current minor release compatible with the actively supported Kubernetes minor releases, i.e.,
19
19
the current release (N), N-1, and N-2. Where possible we will go above and beyond this trying to help our users support
20
20
both newer and older versions of Kubernetes:
21
21
22
-
- For a given Cluster API minor release, we give best-effort support for future Kubernetes versions that are released
22
+
- For a given Cluster API minor release, we give best-effort support for future Kubernetes versions that are released
23
23
during the release's active support period. Depending on the changes made in Kubernetes, users may be required to
24
24
update to the next patch release of Cluster API to maintain compatibility.
25
25
- In some cases where support for future Kubernetes versions can't be added, or is considered not practical or too risky
26
26
adding it, the Kubernetes version support matrix for an existing Cluster API minor release will stop at the last supported version.
27
27
- 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!
28
+
Important! this is not a replacement/alternative for upstream Kubernetes support policies!
29
29
Support for older version of Kubernetes is limited to "Cluster API can start a Cluster with this Kubernetes version"
30
30
and "Cluster API can upgrade to the next Kubernetes version"; it does not include any extended support to Kubernetes itself.
31
31
32
32
Whenever a new Cluster API release is cut, we will document the Kubernetes version compatibility matrix the release
33
33
has been tested with. Summaries of Kubernetes versions supported by each component are additionally maintained in
34
34
the [tables](#release-components) below.
35
35
36
-
On a final comment, let's praise all the contributors keeping care of such a wide support matrix.
36
+
On a final comment, let's praise all the contributors keeping care of such a wide support matrix.
37
37
If someone is looking for opportunities to help with the project, this is definitely an area where additional hands
38
38
and eyes will be more than welcome and greatly beneficial to the entire community.
39
39
@@ -75,7 +75,7 @@ These diagrams show the relationships between components in a Cluster API releas
75
75
| Kubernetes v1.23*|| ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
76
76
| Kubernetes v1.24 |||| ✓ | ✓ | ✓ | ✓ |
77
77
| Kubernetes v1.25 ||||| ✓ | ✓ | ✓ |
78
-
| Kubernetes v1.26 ||||||||
78
+
| Kubernetes v1.26 |||||✓| ✓| ✓|
79
79
80
80
81
81
\* 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.
@@ -99,7 +99,7 @@ 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.
0 commit comments