RKE2 - v1.21.11+rke2r1
This release updates Kubernetes to v1.21.11, fixes a number of minor issues, and includes security updates.
Important Note
This release includes a breaking change to how Cilium helm chart values are customized.
Previously, the cilium CNI was bundled as a subchart of the rke2-cilium chart, and all chart values were nested under the top-level cilium
key within the valuesContent
section. As of this release, the subchart has been removed and nesting is no longer necessary. Chart values should be placed directly within the valuesContent
section.
For example, if you previously had:
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
name: rke2-cilium
namespace: kube-system
spec:
valuesContent: |-
cilium:
ipv6:
enabled: true
That should be converted to:
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
name: rke2-cilium
namespace: kube-system
spec:
valuesContent: |-
ipv6:
enabled: true
Cluster Join Token
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.10+rke2r2:
- Update Cilium to 1.11.2 (#2611)
- Bump containerd to v1.4.13-k3s1 (#2569)
- Remove tag condition for s390x build step (#2555)
- Fix canal bug (#2636)
- Explicitly retag runtime for linux and windows (#2630)
- Add force-restart file when cluster-reset-restore-path is passed (#2658)
- Bump coredns to 1.9.1 (#2656)
- Update K3s and helm-controller (#2661)
- March release v1.21.11 (#2643)
- Revert "[Release-1.21] Explicitly retag runtime for linux and windows" (#2667)
- hardcode linker flag for windows runtime image (#2670)
- Update nginx from hardened2 to hardened4 (#2676)
- Fix uninstall script in SLES systems (#2694)
- Bump K3s version for v1.21 (#2689)
- k3s pin for containerd npipe fix + calico panic fix (#2702)
- Cilium update brings an important change in how the helm chart is consumed when a user wants to set some customized values via helmChartConfig. Please see this link for more details
Packaged Component Versions
| Component | Version |
| --------------- | ------------------------------------------------------------------------------------------------- |
| Kubernetes | v1.21.11 |
| Etcd | v3.4.18.k3s1 |
| Containerd | v1.4.13-k3s1 |
| Runc | v1.0.3 |
| Metrics-server | v0.5.0 |
| CoreDNS | v1.9.1 |
| Ingress-Nginx | 4.0.3 |
| Helm-controller | v0.12.0 |
Available CNIs
| Component | Version | FIPS Compliant |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
| Canal (Default) | Flannel v0.17.0
Calico v3.19.2 | Yes |
| Calico | v3.19.2 | No |
| Cilium | v1.11.2 | 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.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:
- Open issues here
- Join our Slack channel
- Check out our documentation for guidance on how to get started.
Details
- 🔍View and search all RKE2 releases.
- 🛠️Create and share lists to track your tools.
- 🚨Setup notifications for major, security, feature or patch updates.
- 🚀Much more coming soon!