github rancher/rke2 v1.20.11+rke2r1

latest releases: v1.31.3-rc2+rke2r1, v1.30.7-rc2+rke2r1, v1.31.3-rc1+rke2r1...
3 years ago

This release updates Kubernetes to v1.20.11, and fixes a number of minor issues.

For more details on what's new, see the Kubernetes release notes.

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

  • Upgrade Kubernetes to v1.20.11 (#1810)
  • Switched upstream k3s branch from master to engine-1.21 (#1711)
  • Resolved an issue where apiaddresses in etcd were overwritten by pod ips scheduled to server nodes (#1736)
  • Resolved an issue where apiserver cert is missing hostname SAN entries (#1741)
  • Resolved an issue where air-gapped image rewrites failed if path began with "docker.io" (#1785)
  • Resolved an issue where the "etcd-expose-metrics" setting caused the etcd livenessProbe to fail (#1796)

Packaged Component Versions

Component Version
Kubernetes v1.20.11
Etcd v3.4.13-k3s1
Containerd v1.4.9-k3s1
Runc v1.0.1
CNI Plugins v0.8.7
Flannel v0.13.0-rancher1
Calico v3.13.3
Metrics-server v0.3.6
CoreDNS v1.6.9
Ingress-Nginx v1.36.3
Helm-controller v0.10.6

Known Issues

  • #1074 - Control-plane components may fail to start with "bind: address already in use" message. This will be resolved in a future release.
  • #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.20.11+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:

Don't miss a new rke2 release

NewReleases is sending notifications on new releases.