This release updates Kubernetes to v1.28.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.28.4+rke2r1:
- Update stable channel to v1.26.11+rke2r1 (#5099)
- Bump containerd and runc (#5117)
- Bumped containerd/runc to v1.7.10/v1.1.10
- Bump containerd to v1.7.11 (#5129)
- Added support for amazon linux 2023 (#4973)
- Added support for Amazon Linux 2023 (#4973)
- Update to 1.28.5 for december 2023 (#5150)
Charts Versions
| Component | Version |
|---|---|
| rke2-cilium | 1.14.400 |
| rke2-canal | v3.26.3-build2023110900 |
| rke2-calico | v3.26.300 |
| rke2-calico-crd | v3.26.300 |
| rke2-coredns | 1.24.007 |
| rke2-ingress-nginx | 4.8.200 |
| rke2-metrics-server | 2.11.100-build2023051511 |
| rancher-vsphere-csi | 3.0.1-rancher101 |
| rancher-vsphere-cpi | 1.5.100 |
| harvester-cloud-provider | 0.2.200 |
| harvester-csi-driver | 0.1.1600 |
| 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.28.5 |
| Etcd | v3.5.9-k3s1 |
| Containerd | v1.7.11-k3s2 |
| Runc | v1.1.10 |
| Metrics-server | v0.6.3 |
| CoreDNS | v1.10.1 |
| Ingress-Nginx | nginx-1.9.3-hardened1 |
| Helm-controller | v0.15.4 |
Available CNIs
| Component | Version | FIPS Compliant |
|---|---|---|
| Canal (Default) | Flannel v0.23.0 Calico v3.26.3 | Yes |
| Calico | v3.26.3 | No |
| Cilium | v1.14.4 | 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.