rancher/rke2 v1.24.6+rke2r1

on GitHub

This release updates Kubernetes to v1.24.6, 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.24.4+rke2r1:

• Update Cilium version and remove startup-script (#3274)
• Update channel server stable to 1.24.4 (#3269)
• Update canal version (#3272)
• Bump the cilium chart version (#3289)
• Rework vagrant install tests (#3237)
• [release-1.24] Bump containerd v1.6.8 / runc v1.1.4
• The bundled version of runc has been bumped to v1.1.4
• The embedded containerd version has been bumped to v1.6.8-k3s1 (#3301)
• [Release 1.24] Update calico to v3.23.3 (#3318)
• [release-1.24] Fix static pod cleanup when using container-runtime-endpoint (#3332)
• [Release 1.24] Update calico to v3.24.1 (#3343)
• Update for 1.24 patches (#3351)
• Update k8s to 1.24.6 (#3370)

Packaged Component Versions

Available CNIs

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.24.6+rke2r1
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.