A managed Kubernetes service on its own
A cluster from a cloud provider, used directly with tooling the team chooses.
- What you get
- A Kubernetes cluster in your cloud account. The provider runs its control plane and supplies the machines it runs on.
- Good at
- Control. Anything that runs in a container fits, and every part of the setup can be chosen and tuned.
- The trade-off
- Everything between the cluster and a release is yours to assemble: build pipelines, an image registry, traffic routing, certificates, monitoring, backups, and access for developers.
- Choose it when
- The team has Kubernetes experience and time to spend on it, or runs workloads unusual enough that a platform’s conventions would get in the way.