rancher/rke2 v1.23.6+rke2r1

on GitHub

This release updates Kubernetes to v1.23.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.23.5+rke2r1:

• Update developer docs (#2488)
• Mark v1.22.8 stable (#2718)
• Fix windows dev images to include proper runtime tag (#2696)
• Add explicit string to kubeconfig mode in E2E tests (#2706)
• E2E Add option for different CNIs in the validatecluster test (#2703)
• E2E Dualstack CNI Support (#2730)
• Add message in the killall script (#2727)
• Update Kubernetes upgrade documentation (#2736)
• Add --output/-o to secrets-encrypt status (#2681)
• Hide overridden secrets-encryption flag (#2722)
• Remove --with-node-id in docs for rke2 (#2690)
• Remove kube-proxy static pod manifest when --disable-kube-proxy is set (#2731)
• [Docs] Add Secrets Encryption page to navigation (#2663)
• [Docs] Document registry mirror rewrite configuration (#2708)
• Update cilium to support automatic dual-stack config (#2744)
• List downstream release projects (#2739)
• Updating to the latest vSphere charts (#2755)
• Bump harvester cloud provider 0.1.11 (#2754)
• Bump containerd to v1.5.11-k3s1 (#2768)
• Bump Harvester csi to v0.1.11 (#2777)
• E2E: New MixedOS test with linux and windows agents (#2745)
• Bump etcd to v3.5.3-k3s1 (#2763)
• Update k8s to v1.23.6 (#2796)
• Update containerd for Windows (#2801)
• Also inject system-default-registry as global.cattle.systemDefaultRegistry (#2805)
• Bump k3s for April Fixes (#2814)
• Bump containerd for selinux fix (#2820)
• Upgrade ingress nginx chart and images (#2824)

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