Chapter Eleven
Managed Kubernetes
What 'managed' actually means, then EKS, GKE, and AKS in turn, and a framework for deciding between self-managed and managed Kubernetes.
Almost no one should run their own control plane. Managed Kubernetes is the default, and this chapter is about choosing and using it well.
It starts with what 'managed' actually means — the line each provider draws between their responsibility and yours — then walks EKS, GKE, and AKS in turn with their real differences, and closes with a framework for the rare cases where self-managed still makes sense.
Topics in This Chapter
Topic 54
Managed Kubernetes Overview
What a provider manages, what stays yours, and the shared-responsibility line that every comparison comes back to.
Topic 55
Amazon EKS
Kubernetes on AWS — the control-plane model, node groups versus Fargate, IAM integration, and the rough edges to plan around.
Topic 56
Google GKE
Kubernetes from the team that started it — Autopilot versus Standard, release channels, and the deepest native integration of the three.
Topic 57
Azure AKS
Kubernetes on Azure — the free control plane, Entra ID integration, and how node management and add-ons work.
Topic 58
Self-Managed vs Managed
The honest trade-off — control and cost versus operational burden — and the short list of reasons to still run it yourself.