v1.35.3+rke2r1

Release
2026-03-30 ~1 min read github.com #rke2

⚡ TL;DR

Changes since v1.35.2+rke2r1: Charts Versions Packaged Component Versions Available CNIs Helpful Links This release updates Kubernetes to v1.35.3. 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.

📝 Summary

Changes since v1.35.2+rke2r1: Charts Versions Packaged Component Versions Available CNIs Helpful Links This release updates Kubernetes to v1.35.3. 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. --token You may retrieve the token value from any server already joined to the cluster: cat /var/lib/rancher/rke2/server/token Add prime configuration (#9878) prime Bump ingresses 2026 March (#9889) Update to calico v3.31.4 (#9894) Update to calico v3.31.4 (#9894) Bump snapshot crd for groupsnapshot v1beta2 (#9902) Update to multus chart v4.2.403 (#9910) Update to multus chart v4.2.403 (#9910) Update to CoreDNS chart 1.45.205 (#9918) Update to CoreDNS chart 1.45.205 (#9918) Update PSA namespace exceptions (#9927) Bump flannel with newer busybox image (#9935) Version bumps and backports for 2026-03 (#9926) Update to canal v3.31.4-build2026031000 (#9950) Update to canal v3.31.4-build2026031000 (#9950) Bump runc to v1.4.1 (#9955) Pass PRIME_REGISTRY env var to make ci steps (#9963) make ci Add PRIME_REGISTRY passthrough to in-docker-XXXXX targets (#9973) Bump K3s version (#9986) Update to v1.35.3 (#9993) Bump ingress nginx to 1.14.5 (#10004) Add Install Trivy step (#10026) Pin GH Actions to commit sha (#10019) Update to flannel v0.28.2 (#10055) Update to flannel v0.28.2 (#10055) 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.