Honestly I’ve never worked anywhere that made deployment easier for application teams than with Kubernetes. The alternative to infrastructure details leaking ev

Honestly I’ve never worked anywhere that made deployment easier for application teams than with Kubernetes. The alternative to infrastructure details leaking everywhere has historically been a tedious coordination process with an Ops team whose incentive is to say “no” as often as possible. The deployment frequency drops precipitously and consequently the size of changes goes up significantly so when something inevitably breaks you have to sift through tons of changes to find the culprit and you have to coordinate even more to fix the release. And since this one ops team is supporting every team at the company, “coordination” hurts. I’m sure it doesn’t have to be that way—that there are some all-star ops teams who can make a more traditional VM-based infrastructure run as smooth as the median SRE team can build out a Kubernetes platform, but I’ve never seen it. It’s also worth noting that sometimes the details leak because app teams want them to leak—they want to build some feature that requires some particular infrastructure solution (e.g., we want our app to run some background task in response to requests, and we don’t want to do it in the VM lest the autoscaler—which is background-task-agnostic—kill it while the background task is running).