RKE2 - v1.26.3+rke2r1

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

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.26.2+rke2r1:

• Remove root --debug flag (#3955)
• Remove unmounts in killall script (#3954)
• Update Flannel version to v0.21.3 on Canal (#3980)
• Remove unnecessary bits from testing dockerfile (#3975)
• Expand SUC upgrade check to check pods as well as nodes (#3938)
• Don't package empty Windows folder in Linux tar (#3970)
• Bump K3s (#3990)
• Improve uninstallation on RHEL based OS (#3919)
• Update cilim to v1.13.0 (#4003)
• Bump harvester csi driver to v0.1.16 (#3999)
• Update stable channel to v1.24.11+rke2r1 (#4010)
• Bump k3s and containerd (#4015)
• Add automation for Restart command for Rke2 (#3962)
• Update 1.26 and Go (#4033)

Packaged Component Versions

| Component | Version |
| --------------- | ------------------------------------------------------------------------------------------------- |
| Kubernetes | v1.26.3 |
| Etcd | v3.5.5-k3s1 |
| Containerd | v1.6.19-k3s1 |
| Runc | v1.1.4 |
| Metrics-server | v0.6.2 |
| CoreDNS | v1.9.3 |
| Ingress-Nginx | 4.1.0 |
| Helm-controller | v0.13.2 |

Available CNIs

| Component | Version | FIPS Compliant |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
| Canal (Default) | Flannel v0.21.3
Calico v3.25.0 | Yes |
| Calico | v3.25.0 | No |
| Cilium | v1.13.0 | No |
| Multus | v3.9.3 | No |

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.