This message was deleted.

Hey Will, Rancher and our Kubernetes distributions (RKE2/RKE1/k3s) have their own release cycles and therefore, new versions could introduce API changes that negatively impact Rancher. This is why we have the guide that explicitly states the versions of our that are compatible with our distributions. To answer your second question, the support for k8s v1.27 will be included in the next major release i.e. v2.8 per this feature tracking issue..

The Helm chart checks the kubernetes version and refuses to install (it MIGHT work fine with the check removed - kubernetes APIs change a lot less nowadays...) The 2.9 stuff in Github seems to allow 1.27 in the chart... (I deployed a 1.27 cluster for moving our deployment onto a kubeadm cluster (from a RKE1 cluster running on an EoL Ubuntu version) and then had to redeploy onto 1.26 due to this issue)

Didn’t see a planned release date when I perused this GH link — is Rancher released on a set schedule, or “when it’s done”?

This will be our last major release for the year and should be out in early November. Please keep your eyes tuned to our newsletter/other public channels to know when it is generally available.

Thanks @limited-pizza-33551!

Hopefully the new release will run on 1.28... (which is the current version)

Hi @limited-pizza-33551 & community - anxiously awaiting the 2.8 Rancher release, really need to get this running soon - any word on a release date yet? I see the tracker issue https://github.com/rancher/rancher/issues/41720 is almost there…