AttentionThis page documents an earlier version. Go to the latest (v2.3) version.
As highlighted in Kubernetes multi-zone documentation, Kubernetes is by default a single-zone technology. This means workloads will be distributed across multiple nodes of a single Kubernetes cluster running in a single zone. Running a single Kubernetes cluster with nodes present in multiple zones of a single region is possible with additional configuration. Multi-zone Kubernetes clusters have a list of known limitations that users should be aware of.
Amazon Elastic Kubernetes Service and Google Kubernetes Engine supports multi-zone Kubernetes clusters automatically. The following instructions highlight how to deploy a 3-zone YugabyteDB cluster on a 3-zone Kubernetes cluster. Both these deployments use the standard single-zone YugabyteDB Helm Chart to deploy one third of the nodes in the database cluster in each of the 3 zones.