This release resolves issue #1744 by packaging the correct version of Kubernetes for Windows agents.
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/tokenChanges since v1.21.4+rke2r2
- switch to using the build arg KUBERNETES_VERSION over the hardcoded ENV in the windows dockerfile (#1744)
Packaged Component Versions
| Component | Version |
|---|---|
| Kubernetes | v1.21.4 |
| Etcd | v3.4.13-k3s1 |
| Containerd | v1.4.9-k3s1 |
| Runc | v1.0.0 |
| CNI Plugins | v0.8.7 |
| Metrics-server | v0.3.6 |
| CoreDNS | v1.8;3 |
| Ingress-Nginx | 3.34.001 |
| Helm-controller | v0.10.6 |
Available CNIs
| Component | Version | FIPS Compliant |
|---|---|---|
| Canal (Default) | Flannel v0.13.0-rancher1 Calico v3.13.3 | Yes |
| Calico | v3.19.2 | No |
| Cilium | v1.9.8 | 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.4+rke2r3
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-serverHelpful 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.