[oceanplexian]

Yeah imagine if someone built a bridge and was like, yeah, we need to do regular updates or else it will fail and come crashing down.

I feel like software engineers who preach that everything must be connected to the internet and update from the mothership regularly are fundamentally disconnected from reality. If your design is robust to begin with you should be able to depend on it without constantly fiddling with everything.

[terom]

Bridges need regular maintenance or they will fail and come crashing down.

[mcmcmc]

Regular maintenance for bridges means tensioning cables, tightening loose bolts, repainting exposed parts. Not redoing the foundations every month.

[pas]

k8s doesn't require redoing foundations every month

this LTS hysteria is completely made-up

it benefits from updates every year, also who uses naked k8s (the hard way?), folks use a distribution with an updater

[fungalcretin007]

lol. have you ever done an update with breaking api changes and cluster global exposures/rbac for helm charts? It's like switching out the bolts in a running engine.

[pas]

test clusters to the rescue!

of course it's more work than simply applying the new charts, but the nice thing about k8s is that you can dump out the stuff from the working one, use k3s/kind/minikube, try the upgrade, and you are as good to go as with a dist-upgrade or similar.