This message was deleted.
# k3s
a
This message was deleted.
c
nope. Rancher only supports Kubernetes up through 1.24. K3s is up to 1.26 now.
You should check the Rancher support matrix to see what Kubernetes versions it supports.
p
could i still have the standalone rancher manage that cluster? or will it also not be supported
c
nope, not supported means not supported as the local cluster or as a downstream cluster
p
hopefully adding k3s latest support doesnt take too long, but based on this ticket support for 1.25 has been worked on for like a year now 😞 https://github.com/rancher/rancher/issues/38701
c
currently scheduled for 2.7.2
and yeah it is a bit overdue. But 7 months is not quite a year.
The removal of pod security policies, which Rancher used extensively, was a pretty big deal
p
is that why i have the psp notice on the rancher page of all my clusters? From the rancher monitoring stuff?
c
I dunno. its in like everything though.
it was like, THE way to harden things
p
ah, so whats the new way then? We'll be going pci compliant in the near future w/ rancher
c
if you’re just getting started, wait for 2.7.2 and start on a 1.25 cluster so you don’t ever have to touch PSPs
p
too late there we already have several rancher clusters up serving traffic hah