This release updates Kubernetes to v1.29.5.
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/tokenChanges since v1.29.4+rke2r1:
- Update stable channel to v1.28.9+rke2r1 (#5870)
- Add mixedos BGP e2e test (#5859)
- Remove flannel-v6.4096 when rke2-killall.sh (#5795)
- Update e2e test (#5880)
- Remove cni parameter from agent config (#5892)
- Add script to validate flannel versions (#5898)
- Fix mixedosbgp e2e test (#5902)
- E2E GH Action Test (#5908)
- Update k8s v1.29.5 and Go (#5915)
- Windows changes (#5919)
- Cilium version bump to 1.15.5 (#5940)
Charts Versions
| Component | Version |
|---|---|
| rke2-cilium | 1.15.500 |
| rke2-canal | v3.27.3-build2024042301 |
| rke2-calico | v3.27.300 |
| rke2-calico-crd | v3.27.002 |
| rke2-coredns | 1.29.002 |
| rke2-ingress-nginx | 4.9.100 |
| rke2-metrics-server | 3.12.002 |
| rancher-vsphere-csi | 3.1.2-rancher400 |
| rancher-vsphere-cpi | 1.7.001 |
| harvester-cloud-provider | 0.2.300 |
| harvester-csi-driver | 0.1.1700 |
| rke2-snapshot-controller | 1.7.202 |
| rke2-snapshot-controller-crd | 1.7.202 |
| rke2-snapshot-validation-webhook | 1.7.302 |
Packaged Component Versions
| Component | Version |
|---|---|
| Kubernetes | v1.29.5 |
| Etcd | v3.5.9-k3s1 |
| Containerd | v1.7.11-k3s2 |
| Runc | v1.1. |
| Metrics-server | v0.7.1 |
| CoreDNS | v1.11.1 |
| Ingress-Nginx | nginx-1.9.6-hardened1 |
| Helm-controller | v0.15.9 |
Available CNIs
| Component | Version | FIPS Compliant |
|---|---|---|
| Canal (Default) | Flannel v0.25.1 Calico v3.27.3 | Yes |
| Calico | v3.27.3 | No |
| Cilium | v1.15.5 | No |
| Multus | v4.0.2 | 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.