Why Does Developing on Kubernetes Suck?
> Why Does Developing on Kubernetes Suck ?<p>IMHO because we are in a phase of transition.<p>Having worked for years in software industry , I'm convinced we are halfway to a much bigger transformation for Software Engineers / SRE , Developers etc...<p>I work in a Neobank ( N26 , Revolut, etc...) , we are currently in the process of re-writing our entire Core Banking System with MicroServices on top of Kubernetes with Kafka.<p>Not a single day pass without having engineers needing to have an exchange about defining basically all of the the terms that exist within the K8/Docker/Kafa world.<p>- What's a Pod ? How does a pod behave if Kafa goes down ? Do we really need ZooKeeper etc....<p>Their workflows is insanely complex and requires hours if not a day to deploy a single change... obviously let's not even talk about the amount of work our SRE has in the pipe to "package" the entire stack of 150+ services in K8 through a single YAML file....<p>I'm sure this complexity is temporary. One tech will automate all of this away and building , deploying and running will be much simpler.
In it's current shape , K8 remains me of mainframe ecosystem I used to deal with at brick & mortars banks.<p>Powerful systems , but they requires a tremendous amount of work and experts to be properly managed and take full advantage of it. 
Just like mainframes , K8 leaves very little room for "mistakes" or "approximation".