Hey 
I was on the infrastructure team managing our Kubernetes, and now I’m a customer of our Kubernetes in a different team (I write a lot of services)
but I’ve also seen quite a lot of these systems in the wild and it turns out that shoving the network in the middle of your app is complex.
Genuinely we have amazing tooling. People who build microservices will never need to think about any of the networking or Kubernetes side. It’s kind of like Heroku, you don’t think about hosting your app. You just git push and it’s all done for you 
(When I say kind of, I am using this very fuzzily. There are CI checks + reviews + automated rollbacks etc. See Will’s blog post below)
Basically I hope that they have completely abstracted away the distributed nature of things from the app developers, because if they haven’t then it’s going to be an ocean of pain.
Not “completely”. Some developers need access to Kubernete specific things. As an example they may build a service which cannot fail, so they want 10 replicas. They can do this quite easily with a neat lil YAML file.
But yes, the average developer will not need to think about Kubernetes.
In fact, I’d really love to see a blog post on “How Monzo does Microservices and how we avoid it being an ocean of pain“.
Will works on the team which creates the tooling for “avoiding it being an ocean of pain”. His blog post is good