This release updates Kubernetes to v1.29.12.
Important Note
If your server (control-plane) nodes were not started with the --token
CLI flag or config file key, a randomized token was generated during initial cluster startup. This key is used both for joining new nodes to the cluster, and for encrypting cluster bootstrap data within the datastore. Ensure that you retain a copy of this token, as is required when restoring from backup.
You may retrieve the token value from any server already joined to the cluster:
cat /var/lib/rancher/rke2/server/token
Changes since v1.29.11+rke2r1:
- Update to Cilium v1.16.4 (#7327)
- Updated Calico version to
v3.29.1
(#7353) - Bump harvester csi driver v0.1.21 (#7285)
- Bump Harvester-csi-driver v0.1.21
- Update k3s for loadbalancer improvements (#7399)
- Update Flannel and Canal version (#7408)
- Bump ingress-nginx to hardened6 (#7414)
- Bump dns-node-cache to 1.24.0 (#7420)
- Bump hardened k8s and build base (#7426)
Charts Versions
Component | Version |
---|---|
rke2-cilium | 1.16.400 |
rke2-canal | v3.29.1-build2024121100 |
rke2-calico | v3.29.100 |
rke2-calico-crd | v3.29.100 |
rke2-coredns | 1.36.102 |
rke2-ingress-nginx | 4.10.503 |
rke2-metrics-server | 3.12.004 |
rancher-vsphere-csi | 3.3.1-rancher700 |
rancher-vsphere-cpi | 1.9.100 |
harvester-cloud-provider | 0.2.600 |
harvester-csi-driver | 0.1.2100 |
rke2-snapshot-controller | 3.0.601 |
rke2-snapshot-controller-crd | 3.0.601 |
rke2-snapshot-validation-webhook | 1.9.001 |
Packaged Component Versions
Component | Version |
---|---|
Kubernetes | v1.29.12 |
Etcd | v3.5.16-k3s1 |
Containerd | v1.7.23-k3s2 |
Runc | v1.1.14 |
Metrics-server | v0.7.1 |
CoreDNS | v1.12.0 |
Ingress-Nginx | v1.10.5-hardened6 |
Helm-controller | v0.15.15 |
Available CNIs
Component | Version | FIPS Compliant |
---|---|---|
Canal (Default) | Flannel v0.26.1 Calico v3.29.1 | Yes |
Calico | v3.29.1 | No |
Cilium | v1.16.4 | No |
Multus | v4.1.3 | No |
Helpful Links
As always, we welcome and appreciate feedback from our community of users. Please feel free to:
- Open issues here
- Join our Slack channel
- Check out our documentation for guidance on how to get started.