4 — Cluster API
Purpose
[stub: cluster-api]
Metadata
| Author | Amit Singh |
| Scope | kubernetes |
Local graph
Related notes
1 — AKS
AKS makes the control plane free specifically so Azure can win on node-hour billing, which is why the real cost and design battle moves to node pool sizing, availability zones, and Azure CNI IP exhaustion.
2 — EKS
EKS charges for the control plane yet still leaves CoreDNS, kube-proxy, and the CNI as self-managed add-ons, proving that 'managed Kubernetes' is a spectrum of responsibility rather than a single guarantee.
5 — Federation
KubeFed's decline in favor of GitOps-pushed manifests showed that replicating API objects across clusters is the wrong abstraction — the failure mode isn't the sync mechanism, it's treating clusters as one logical API server.
3 — GKE
GKE Autopilot bills per-pod resource request rather than per-node, which inverts the usual capacity-planning problem by making the scheduler itself the thing you optimize for cost, not the node pool.