RKE2 - v1.27.10+rke2r1

This release updates Kubernetes to v1.27.10.

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

• Use dl.k8s.io for getting kubectl (#5180)
• Ensure charts directory exists in Windows runtime image (#5186)
• Bump versions of different components (#5168)
• Update coredns chart to fix bug (#5201)
• Update multus chart to add optional dhcp daemonset (#5211)
• Add e2e test about dnscache (#5227)
• Update rke2-whereabouts to v0.6.3 and bump rke2-multus parent chart (#5245)
• Bump sriov image build versions (#5255)
• Enable arm64 based images for calico, multus and harvester (#5266)
• Improve kube-proxy and calico logging in Windows (#5285)
• Bump k3s for v1.27 (#5270)
• Update to 1.27.10 (#5294)
• Update base image (#5307)
• Bump K3s and runc versions for v1.27 (#5351)

Packaged Component Versions

| Component | Version |
| --------------- | --------------------------------------------------------------------------------------------------- |
| Kubernetes | v1.27.10 |
| Etcd | v3.5.9-k3s1 |
| Containerd | v1.7.11-k3s2 |
| Runc | v1.1. |
| Metrics-server | v0.6.3 |
| CoreDNS | v1.10.1 |
| Ingress-Nginx | |
| Helm-controller | v0.15.8 |

Available CNIs

| Component | Version | FIPS Compliant |
| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
| Canal (Default) | Flannel v0.23.0
Calico v3.26.3 | Yes |
| Calico | v3.26.3 | No |
| Cilium | v1.14.4 | No |
| Multus | v4.0.2 | 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.