That's why Kubernetes provides versioned APIs with proper lifecycles and levels of stability. A stable API is not going to change randomly on you, and of it do

That's why Kubernetes provides versioned APIs with proper lifecycles and levels of stability. A stable API is not going to change randomly on you, and of it does, it's going to come with deprecation policy so you have time to do it. Personally I did have few "painful" k8s upgrades, but every time it happened it was due to long-announced large scale change... That another team didn't want to upgrade over despite delaying so long the last version compatible became EOL