Kubernetes is powerful, well designed and the industry standard for running containers. I still don't like it. What bothers me is what it demands from the team that has to run it: a lot of knowledge, constant maintenance and a cost that never shows up on the architecture diagram.
Every time Amazon EKS comes up in a design discussion, it's justified with the same two arguments: we need it to be portable, and it's the industry standard. Both are partly right. In this article I explain why neither convinces me on its own, and when I do choose Kubernetes.
Note: It's a personal opinion, based on my experience as an architect, and it doesn't apply to every context: if yours is different, your conclusion may reasonably be different too.
I'll go in this order: what Kubernetes demands, the two arguments used to justify it (portability and being the industry standard) and when I do choose it.
The basics of Kubernetes and Amazon EKS are in Part 1 of my series on my blog , and the comparison between AWS Lambda,…