148422597X Kubernetes Management Design Patterns [Vohra 2017-01-29] {E559F6BB}

Chapter 4 ■ Using Multiple Zones
Alternatively obtain the Node IP as follows:
kubectl describe deployment nginx | grep Node
The Node IP is output as shown in Figure 4-38.
Figure 4-38. A PersistentVolumeClaim claim1.json
Next, list the node labels:
kubectl get node <node ip> --show-labels
The node is running in the zone us-east-1b, which is the same as the zone of the persistent volume, as
shown in Figure 4-39.
Figure 4-39. A node is scheduled on the same zone as the persistent volume
Summary
In this chapter we created a Kubernetes cluster using multiple zones on CoreOS. A multi-zone cluster is
a highly available cluster. A multi-zone cluster is configured by specifying multiple Kubernetes subnets
with their CIDRs and availability zones in cluster.yaml in the subnets section. We also discussed creating a
multi-zone cluster on the AWS cloud provider by setting the MULTIZONE parameter to true in the curl -sS
https://get.k8s.io command to launch a Kubernetes cluster. In the next chapter we will discuss using the
Tectonic console.
116