Kelkonosemmel
I plan to buy a farm when I have the money and I'm pretty sure while I will/want to do a lot of hands on renovation and sculpting (park, etc) long term some type of robot should be good and affordable enough to take over when I'm too old.
I'm upgrading k8s for years now, had very rarely issues.
Independent of it if you really have big workloads it's the right thing anyway to have a good team behind it.
Nonetheless if you use gke for example I and no complicated plugins, it's basically automatic.
Shouldn't be the tooling around it good enough that a few prompt papers don't overload the system?
I found actions easier to use
But my preferred way is in place as it's easy: upgrade one Ctrl plane node after the other, than upgrade every node or create a new one and move your workload.
The power of k8s is of course shit when you only move legacy garbage into the cloud as those are not ha at all.
But lucky enough people slowly learn how to write apps cloud native.
You can't get a really old k8s version on gke
You need to keep updating it!
No legacy 10 year old garbage in the corner just because managers don't understand that this is shit.
And for me it's the perfect excuse NOT having those garbage discussions.
And honestly k8s doesn't change that much anyway
It's the time to get feedback and improve.
The problem is: if people are stuck and don't learn the code review phase will always stay as a long thing.
The whole team is responsible for security, maintainability, etc.
I don't care about some code monkey able to write some code or fixing something. I care about a team, a product.
Your attitude would not work in my team, which is fine
For making more money for 5 years or so to retire earlier.
But than I think about the bigger social gap and dislike the idea again.