rancher/rke2 v1.25.3+rke2r1

on GitHub

This release update Kubernetes to v1.25.3+rke2r1, 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.25.2+rke2r1:

• Update docs with extra option (#3336)
• Upgrade Calico version on Windows (#3346)
• Update docs with iptables requirement on canal and calico (#3367)
• Add support for Calico interface overrides for Windows (#3375)
• Update latest in channels.yaml to v1.24.6+rke2r1 (#3389)
• Bump vsphere csi/cpi charts and images (#3356)
• The embedded metrics-server version has been bumped to v0.6.1 (#3399)
• Update docs for multus with cilium (#3326)
• Bump k3s for servicelb ccm change; add servicelb support (#3404)
• Add v1.25 channel to the channel server (#3382)
• Allow CNI none on windows (#3403)
• Update fips_support.md (#3405)
• Change static pod uid/hash generation/checking (#3415)
• Pass through kubelet-args to temporary kubelet (#3418)
• Initial terraform automation (#3390)
• Bump vsphere CSI to v2.6.1 (#3420)
• Updated Canal chart to fix token renewal from calico-node (#3426)
• E2E: Parallel and Logging Improvements (#3433)
• Bump K3s version for v1.25 (#3434)
• Update canal to v3.24.1 (#3444)
• Update release docs to include content discussed during release retro (#3421)
• Update documentation with PSP removal (#3360)
• October RKE2 K8s Update v1.25.3 (#3460)
• Bump CCM image tag (#3465)
• Add fapolicyd configuration rules (#3416)
• Prevent script fail when fapolicyd doesn't exist (#3478)

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