diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3e6ad5a3aa28..9ba9245f46eb 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -392,10 +392,10 @@ Examples: ```bash $ kubectl get kubeadmcontrolplane NAMESPACE NAME INITIALIZED API SERVER AVAILABLE REPLICAS READY UPDATED UNAVAILABLE AGE VERSION -quick-start-d5ufye quick-start-ntysk0-control-plane true true 1 1 1 2m44s v1.23.3 +quick-start-d5ufye quick-start-ntysk0-control-plane true true 1 1 1 2m44s v1.24.0 $ kubectl get machinedeployment NAMESPACE NAME CLUSTER REPLICAS READY UPDATED UNAVAILABLE PHASE AGE VERSION -quick-start-d5ufye quick-start-ntysk0-md-0 quick-start-ntysk0 1 1 1 ScalingUp 3m28s v1.23.3 +quick-start-d5ufye quick-start-ntysk0-md-0 quick-start-ntysk0 1 1 1 ScalingUp 3m28s v1.24.0 ``` ## Google Doc Viewing Permissions diff --git a/docs/book/src/reference/versions.md b/docs/book/src/reference/versions.md index ce2e2adf33bb..05fc10ebc577 100644 --- a/docs/book/src/reference/versions.md +++ b/docs/book/src/reference/versions.md @@ -63,16 +63,17 @@ These diagrams show the relationships between components in a Cluster API releas #### Core Provider (`cluster-api-controller`) -| | 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 | -| ---------------- | -------------------------------- | ----------------------------- | -------------------------------- | ----------------------------- | -------------------------------- | ----------------------------- | -| Kubernetes v1.16 | ✓ | ✓ | | | | | -| Kubernetes v1.17 | ✓ | ✓ | | | | | -| Kubernetes v1.18 | ✓ | ✓ | | ✓ | | ✓ | -| Kubernetes v1.19 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.20 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.21 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.22 | | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.23* | | | ✓ | ✓ | ✓ | ✓ | +| | 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 | +|-------------------|---------------------------------|-------------------------------|---------------------------------|-------------------------------|--------------------------------|------------------------------| +| Kubernetes v1.16 | ✓ | ✓ | | | | | +| Kubernetes v1.17 | ✓ | ✓ | | | | | +| Kubernetes v1.18 | ✓ | ✓ | | ✓ | | ✓ | +| Kubernetes v1.19 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.20 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.21 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.22 | | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.23* | | | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.24 | | | ✓ | ✓ | ✓ | ✓ | \* 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. Previous Kubernetes **minor** versions are not affected. @@ -81,31 +82,33 @@ The Core Provider also talks to API server of every Workload Cluster. Therefore, #### Kubeadm Bootstrap Provider (`kubeadm-bootstrap-controller`) -| | 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 | -| ---------------------------------- | -------------------------------- | ----------------------------- | ------------------------------- | ----------------------------- | ------------------------------- | ----------------------------- | -| Kubernetes v1.16 + kubeadm/v1beta2 | ✓ | ✓ | | | | | -| Kubernetes v1.17 + kubeadm/v1beta2 | ✓ | ✓ | | | | | -| Kubernetes v1.18 + kubeadm/v1beta2 | ✓ | ✓ | | ✓ | | ✓ | -| Kubernetes v1.19 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.20 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.21 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.22 + kubeadm/v1beta2 (v0.3) kubeadm/v1beta3 (v0.4+) | | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.23 + kubeadm/v1beta3 | | | ✓ | ✓ | ✓ | ✓ | +| | 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 | +|-------------------------------------------------------------------|---------------------------------|-------------------------------|---------------------------------|-------------------------------|--------------------------------|------------------------------| +| Kubernetes v1.16 + kubeadm/v1beta2 | ✓ | ✓ | | | | | +| Kubernetes v1.17 + kubeadm/v1beta2 | ✓ | ✓ | | | | | +| Kubernetes v1.18 + kubeadm/v1beta2 | ✓ | ✓ | | ✓ | | ✓ | +| Kubernetes v1.19 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.20 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.21 + kubeadm/v1beta2 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.22 + kubeadm/v1beta2 (v0.3) kubeadm/v1beta3 (v0.4+) | | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.23 + kubeadm/v1beta3 | | | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.24 + kubeadm/v1beta3 | | | ✓ | ✓ | ✓ | ✓ | The Kubeadm Bootstrap Provider generates kubeadm configuration using the API version recommended for the target Kubernetes version. #### Kubeadm Control Plane Provider (`kubeadm-control-plane-controller`) | | 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 | -| -------------------------- | ------------------------------- |-------------------------------|---------------------------------|-------------------------------| ------------------------------- | ----------------------------- | -| Kubernetes v1.16 + etcd/v3 | ✓ | ✓ | | | | | -| Kubernetes v1.17 + etcd/v3 | ✓ | ✓ | | | | | -| Kubernetes v1.18 + etcd/v3 | ✓ | ✓ | | ✓ | | ✓ | -| Kubernetes v1.19 + etcd/v3 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.20 + etcd/v3 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.21 + etcd/v3 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.22 + etcd/v3 | | ✓* | ✓ | ✓ | ✓ | ✓ | -| Kubernetes v1.23 + etcd/v3 | | | ✓* | ✓* | ✓ | ✓ | +|----------------------------|---------------------------------|-------------------------------|---------------------------------|-------------------------------|--------------------------------|------------------------------| +| Kubernetes v1.16 + etcd/v3 | ✓ | ✓ | | | | | +| Kubernetes v1.17 + etcd/v3 | ✓ | ✓ | | | | | +| Kubernetes v1.18 + etcd/v3 | ✓ | ✓ | | ✓ | | ✓ | +| Kubernetes v1.19 + etcd/v3 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.20 + etcd/v3 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.21 + etcd/v3 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.22 + etcd/v3 | | ✓* | ✓ | ✓ | ✓ | ✓ | +| Kubernetes v1.23 + etcd/v3 | | | ✓* | ✓* | ✓ | ✓ | +| Kubernetes v1.24 + etcd/v3 | | | ✓* | ✓* | ✓ | ✓ | 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. diff --git a/docs/book/src/user/quick-start.md b/docs/book/src/user/quick-start.md index 14eaaf00cd96..cabdffadeccb 100644 --- a/docs/book/src/user/quick-start.md +++ b/docs/book/src/user/quick-start.md @@ -715,7 +715,7 @@ For the purpose of this tutorial, we'll name our cluster capi-quickstart. ```bash clusterctl generate cluster capi-quickstart \ - --kubernetes-version v1.23.3 \ + --kubernetes-version v1.24.0 \ --control-plane-machine-count=3 \ --worker-machine-count=3 \ > capi-quickstart.yaml @@ -734,7 +734,7 @@ The Docker provider is not designed for production use and is intended for devel ```bash clusterctl generate cluster capi-quickstart --flavor development \ - --kubernetes-version v1.23.3 \ + --kubernetes-version v1.24.0 \ --control-plane-machine-count=3 \ --worker-machine-count=3 \ > capi-quickstart.yaml @@ -744,7 +744,7 @@ To create a Cluster with ClusterClass: ```bash clusterctl generate cluster capi-quickstart --flavor development-topology \ - --kubernetes-version v1.23.3 \ + --kubernetes-version v1.24.0 \ --control-plane-machine-count=3 \ --worker-machine-count=3 \ > capi-quickstart.yaml @@ -804,7 +804,7 @@ You should see an output is similar to this: ```bash NAME INITIALIZED API SERVER AVAILABLE VERSION REPLICAS READY UPDATED UNAVAILABLE -capi-quickstart-control-plane true v1.23.3 3 3 3 +capi-quickstart-control-plane true v1.24.0 3 3 3 ```