This message was deleted.
# general
a
This message was deleted.
šŸ‘€ 3
b
glad to help as I have a vested interest in getting lasso on k8s 1.26, but there isn't a controller-runtime release out yet that supports 1.26, I assume that will happen as soon as v1.26 is released upstream.
On the positive side you can finally drop https://github.com/rancher/client-go/commit/98676c353a3009fe8c21013484cc3d151ecfb594 as the behavior is supported upstream now
c
I think everyone’s still trying to figure out what to do about PSPs going away for 1.25; it’s a big reason that rancher and RKE don’t support it yet. We’ve started in on 1.26 for k3s and rke2 but I doubt anyone on the Rancher side has even looked at it yet.
r
I can tell you that we've looked into the general direction of 1.26 support, and it looms, ever-so-distantly on the horizon of our future. šŸ˜‰
b
I rancher supporting only up to 1.24 right now?
c
yeah 2.7 still only supports 1.23 and 1.24
r
Indeed. Once we tackle the PSP/PSA situation, we're slated to add support for 1.25 somewhere in early 2023.
But don't quote me on that.
c
gonna be fun when 1.26 comes out next month and Rancher has only one non-EOL version that it supports
b
oh no, that's enterprise. you pay more for EOL. It's a feature.
šŸ˜„ 4
šŸ˜… 3
šŸ˜† 2
c
lol
r
This enterprise is in its own bubble it seems. PSP/PSA was deprecated in v1.21, first half of 2021.
b
What is ā€œthis enterpriseā€ referring to. Doesn’t matter if it was deprecated 5 years ago. Do you know how hard it is for enterprise to adapt, especially when it’s a security component leveraged by thousands of apps?
r
Would be much harder backporting all bugfixes/security patches from upstream tho. Yeah, it wasn't like it was removed from Kubernetes just like that.
b
I’m not sure the point you are getting at but I really don’t think you understand the complexity of enterprise and the cost modeling. But obviously Rancher is going to support newer version. Its just harder when k8s makes major breaking changes and takes them a bit longer.
391 Views