Same Kubernetes API, different operational opinions. The cloud handles the control plane (etcd, API server, scheduler) and patches it; you bring the worker nodes (or use a serverless mode) and the workloads. Pick by where the rest of your data lives.
← Back to DevOps & CI/CD| Service | Strengths | Watch out for |
|---|---|---|
| GKE (Google) | Most polished K8s experience. Autopilot mode hides nodes entirely. Aggressive feature releases since K8s came from Google. | GCP regional footprint smaller than AWS. |
| EKS (AWS) | Tightest integration with the broader AWS surface (IAM, ALB, EBS, VPC). Fargate for serverless pods. | Most assembly required. IAM-for-pods (IRSA / Pod Identity), CNI, ALB controller — all bring-your-own. |
| AKS (Azure) | Free control plane on the standard tier. Strong AAD/Entra integration. Decent Windows-node support. | Some addons lag GKE/EKS; networking models (Azure CNI vs kubenet vs Cilium) are confusing. |
All three are great for "just run my pods" workloads; less great when you need GPUs, host-level access, or persistent local disks.