v1.21.14+rke2r1

This release updates Kubernetes to v1.21.14, fixes a number of minor issues, and includes security updates.

Important Notes

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.21.13+rke2r2:

• Add Static Pod Startup Hook + K3s Bump + CoreDNS bump (#3068)
• June patch 1.21 (#3085)
• Double number of steps for criBackoff

Packaged Component Versions

Component	Version
Kubernetes	v1.21.14
Etcd	v3.4.18
Containerd	v1.4.13-k3s1
Runc	v1.0.3
Metrics-server	v0.5.0
CoreDNS	v1.9.3
Ingress-Nginx	4.1.0
Helm-controller	v0.12.1

Available CNIs

Component	Version	FIPS Compliant
Canal (Default)	Flannel v0.17.0 Calico v3.21.4	Yes
Calico	v3.19.2	No
Cilium	v1.11.5	No
Multus	v3.7.1	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.21.14+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.