This release updates Kubernetes to v1.22.10, fixes a number of minor issues, and includes security updates.
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.22.9+rke2r2:
- [Release 1.22] Updating the vSphere CPI chart version. (#2870)
- [Release 1.22] Update Cilium version (#2876)
- [Release 1.22] Update Calico in 1.22 (#2888)
- [Release 1.22] Updated canal to 3.22.2 (#2910)
- Update calico to newest version to fix bug (#2902)
- [Release 1.22] Update multus to the latest chart version (#2923)
- [Release 1.22] Move windows dependencies check to CI (#2880) (#2916)
- [Release 1.22] Support dev rpm creation and installation (#2937)
- [Release 1.22] Ignore windows binaries when creating linux bundle (#2946)
- [Release 1.22] Fixed IPv6 only support (#2956)
- [Release 1.22] Bump k3s and etcd (#2856)
- [Release 1.22] Fixed canal chart for IPv6 only setup (#2976)
- [Release 1.22] Update Cilium to 1.11.5 (#2975)
- Upgrade kubernetes to v1.22.10 (#2993)
- [Release 1.22] Disable egress-selector for calico/multus/none (#3014)
- [Release 1.22] Bump containerd, runc, k3s (#3021)
- [Release 1.22] Remove cni-based egress-selector config and bump k3s (#3027)
- May release v1.22.10+rke2r2 (#3031)
- [Release 1.22] Unconditionally set egress-selector-mode to disabled (#3037)
Packaged Component Versions
Component | Version |
---|---|
Kubernetes | v1.22.10 |
Etcd | v3.5.4-k3s1 |
Containerd | v1.5.13-k3s1 |
Runc | v1.1.2 |
Metrics-server | v0.5.0 |
CoreDNS | v1.9.1 |
Ingress-Nginx | 4.1.0 |
Helm-controller | v0.12.1 |
Available CNIs
Component | Version | FIPS Compliant |
---|---|---|
Canal (Default) | Flannel v0.17.0 Calico v3.22.2 | Yes |
Calico | v3.21.5 | No |
Cilium | v1.11.5 | No |
Multus | v3.8 | No |
Known Issues
- #1447 - When restoring RKE2 from backup to a new node, you should ensure that all pods are stopped following the initial restore:
curl -sfL https://get.rke2.io | sudo INSTALL_RKE2_VERSION=v1.22.10+rke2r2
rke2 server \
--cluster-reset \
--cluster-reset-restore-path=<PATH-TO-SNAPSHOT> --token <token used in the original cluster>
rke2-killall.sh
systemctl enable rke2-server
systemctl start rke2-server
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.