This release updates Kubernetes to v1.19.15, and fixes a number of minor issues.
For more details on what's new, see the Kubernetes release 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:
Changes since v1.19.14+rke2r1
- Upgrade Kubernetes to v1.19.15 (#1809)
- Resolved an issue where passing cluster-reset fails to trigger reset (#1574)
- Resolved an issue where apiaddresses in etcd were overwritten by pod ips scheduled to server nodes (#1737)
Packaged Component Versions
- #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.19.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
As always, we welcome and appreciate feedback from our community of users. Please feel free to: