Maybe for companies that employ many devopses, but most of my clients already have only one or two. That is, me with eventually a junior that I'm getting up to

Maybe for companies that employ many devopses, but most of my clients already have only one or two. That is, me with eventually a junior that I'm getting up to speed so he can take my place. Furthermore, the "run" part is only a fraction of the job, the whole pilgrimage from developers' code to a production-ready container is most of the work, and that's very client-specific. For example, I will always have a high-paying job at making workflows that help ensuring average developers cannot send bad code in production, that they are reviewed etc. Kubernetes is great because the "run" part was really the low-hanging fruit. A container is a container, and setting up routing, provisioning etc is very generic and boring.