This message was deleted.

on the CNI side, we are using cilium in kubeproxymode set to disabled i.e. we are still using iptables not ebpf

we are attempting a direct jump from 1.22 to 1.26 version of RKE2

That is absolutely, positively not supported.

yeah am aware that’s usually not recommended but we had success with some direct jumps in the past , it’s just what we are unlucky this time due to some API deprecations

yeahhhh just don’t. Just because it works sometimes for some versions doesn’t mean you should to it.

thanks for the inputs, yeah will keep that in mind some more context, we upgrade kubernetes along with our product offering every 6 months and we support it for 3 years but k8's has life cycle of 14 months and since we support it for 3 years, customers don’t care upgrading to recent version and once they are out of support after 3 years , they try to upgrade to latest version available in the market as they don’t want to go through the pain of all intermediate jumps

yeah, you might need to do some customer education, or come up with a better way to handle that.