In one sentence: Everybody already knows how to use SSH, only the infra department knows how to use kubectl. Don’t underestimate how much pushback and struggle

In one sentence: Everybody already knows how to use SSH, only the infra department knows how to use kubectl. Don’t underestimate how much pushback and struggle even such a small tool addition can add to developers with already too many other things on their mind. This enables the whole dev org to use ephemeral workflow from k8s, without having to understanding k8s. SSH also comes with a lot of tooling integration that is not as readily available as for k8s. Tunneling through anything, IDE integration or sshfs to name a few. Granularly locking down a k8s cluster can also be a challenge. It’s easier to just block your k8s api server from anyone who is not admin. Otherwise in principle you are right, kubectl should on paper be equally or even more capable.