This release updates Kubernetes to v1.32.9.
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.32.8+rke2r1:
- Added Calico new images (#8830)
- Added Cilium with wireguard e2e tests (#8815)
- CNI and coredns bumps for Sep 25 release (#8847)
- Bump k3s, containerd, runc (#8866)
- Bump crictl and cloud provider (#8863)
- Bump ingress-nginx v1.12.6-hardened1 (#8870)
- Bump CNI chart latest version (#8884)
- Update metrics-server chart 3.13.001 (#8905)
- Update CoreDNS chart 1.43.302 (#8909)
- Bump etcd (#8911)
- Update to v1.32.9 and Go v1.23.12 (#8917)
- Bump vsphere charts (#8940)
Charts Versions
Component | Version |
---|---|
rke2-cilium | 1.18.103 |
rke2-canal | v3.30.3-build2025090900 |
rke2-calico | v3.30.300 |
rke2-calico-crd | v3.30.300 |
rke2-coredns | 1.43.302 |
rke2-ingress-nginx | 4.12.600 |
rke2-metrics-server | 3.13.001 |
rancher-vsphere-csi | 3.5.0-rancher100 |
rancher-vsphere-cpi | 1.12.100 |
harvester-cloud-provider | 0.2.1000 |
harvester-csi-driver | 0.1.2400 |
rke2-snapshot-controller | 4.0.003 |
rke2-snapshot-controller-crd | 4.0.003 |
rke2-snapshot-validation-webhook | 0.0.0 |
Packaged Component Versions
Component | Version |
---|---|
Kubernetes | v1.32.9 |
Etcd | v3.5.21-k3s1 |
Containerd | v2.1.4-k3s2 |
Runc | v1.3.1 |
Metrics-server | v0.8.0 |
CoreDNS | v1.12.3 |
Ingress-Nginx | v1.12.6-hardened1 |
Helm-controller | v0.16.13 |
Available CNIs
Component | Version | FIPS Compliant |
---|---|---|
Canal (Default) | Flannel v0.27.3 Calico v3.30.3 | Yes |
Calico | v3.30.3 | No |
Cilium | v1.18.1 | No |
Multus | v4.2.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.