7 ms·
Many comments here disagreeing about LTS just because it won't be up-to-date – are missing a critical point. When people run a rolling release on their server,
by rdsubhas 3y ago
Many comments here disagreeing about LTS just because it won't be up-to-date – are missing a critical point.
When people run a rolling release on their server, their original intent is "Yay I'll force myself to be up-to-date". Reality is, they get conflicts on installed 3rd party software in each upgrade. What ends up happening is, they get frozen on some point in time, without even security patches for a long time.
k8s is like an OS, it's not just the core components, there is <ingress/ gateway/ mesh/ overlays/ operators/ admission controllers/ 3rd party integrations like vault, autoscalers, etc>. Something or the other breaks with each rolling release. I've grown really tired of the way GKE v1.25 pretends to be a "minor" automated upgrade, when it removes or changes god knows how many APIs.
This is what is happening in kubernetes land. The broken upgrade fatigue is real, but it's hampered by wishful thinking.
- houseofzeus 3y agoWell, that and there appears to at least be a commercial market for an LTS based on announcements from Red Hat, Azure, and now Amazon. Azure are the ones who effectively posed the question in the community of hey, since we all appear to be doing this is there any value in collaborating on it in the open by rebooting the LTS working group. Now that said, while you are absolutely right that third party solutions are the biggest boat anchor to users upgrading whether commercial or open source, they are also the reason an LTS doesn't necessarily fix much because then those things need an LTS too and/or they decide hey this is great we will fix on this one and it becomes an even bigger lift when the ISV does need to bring their stuff up to latest.