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

marco.cirilli
from marco.cirilli More from this publisher
19.06.2021 Views

Chapter 4 ■ Using Multiple ZonesFigure 4-25. The same master IP but a different subnet CIDRThe EC2 console lists another set of nodes in a different zone, us-east-1b as shown in Figure 4-26. Thecluster has only one master in zone us-east-1c but minions in different zones, us-east-1b and us-east-1c.Figure 4-26. The same master IP but a different subnet CIDR107

Chapter 4 ■ Using Multiple ZonesListing the nodes displays six nodes, as shown in Figure 4-27.Figure 4-27. Listing nodes in two different zonesListing the nodes including the labels displays six nodes, three in the us-east-1c zone and three in useast-1b,as shown in Figure 4-28.Figure 4-28. Listing nodes in two zones including labelsLaunch another node set in the us-east-1d zone using the same master node. Specify a differentsubnet CIDR for the us-east-1d zone.KUBE_USE_EXISTING_MASTER=true MULTIZONE=true KUBERNETES_PROVIDER=aws KUBE_AWS_ZONE=us-east-1d NUM_NODES=3 KUBE_SUBNET_CIDR=172.20.2.0/24 MASTER_INTERNAL_IP=172.20.0.9 kubernetes/cluster/kube-up.sh108

Chapter 4 ■ Using Multiple Zones

Figure 4-25. The same master IP but a different subnet CIDR

The EC2 console lists another set of nodes in a different zone, us-east-1b as shown in Figure 4-26. The

cluster has only one master in zone us-east-1c but minions in different zones, us-east-1b and us-east-1c.

Figure 4-26. The same master IP but a different subnet CIDR

107

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!