rancher/rke2 v1.23.15+rke2r1

on GitHub

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

• Add more tests to the windows env (#3607)
• Update Canal version (#3627)
• [Backport 1.23] update multus chart to v3.9-build2022102805 (#3637)
• [Backport 1.23] update rke2-calico chart to v3.24.501 (#3631)
• Backports for 2022-12 (#3649)
• Updated cilium version and added new cilium images (#3644)
• Bump ingress-nginx to 1.4.1 (#3654)
• Update to version 1.23.15 (#3658)
• Bump K3s and containerd versions for v1.23 (#3677)
• [Backport v1.23] Fixed cilium chart when enabled hubble images (#3690)
• Bump ingress-nginx (#3704)

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.23.15+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.