Any decent k8s engineer worth his salt should find it pretty easy to navigate this, since how you deal with that is pretty standardised.

I've written custom operators and submitted upstream patches to existing-ones, it's not that hard once you know what you're dealing with conceptually.

So your point is that once you learn how to use the tool it's easier to use the tool?

Also, what is a k8s engineer? What's the difference between this engineer and a "devops" engineer? This and software engineer?

> So your point is that once you learn how to use the tool it's easier to use the tool?

Kubernetes is not just "a tool", it's a platform. So if you know the k8s fundamentals, being dropped in an unfamiliar environment should not be a problem. It's the same as knowing your way around a Linux system, you might not be familiar with that specific distribution you're thrown into, but you should be able to explore the system and figure stuff out.

> Also, what is a k8s engineer? What's the difference between this engineer and a "devops" engineer? This and software engineer?

Any engineer who claims to know a bit more than the basics of k8s? It being a software, "devops", SRE, "platform", ... engineer doesn't really matter, I've been labeled all of the above.

I'll never claim k8s is perfect, I have plenty of issues with it, but very few of them are an architectural problem, and I've yet to encounter a platform that attempts to address all the issues k8s does. But you seem to be very critical of it, so what would you propose as a viable alternative?