anchor.diff:  ip-172-20-63-55.ec2.internal  node  True
   ip-172-20-75-78.ec2.internal  node  True
   
  -Your cluster cluster.k8s.local is ready
  +Your cluster example.cluster.k8s.local is ready
   ```
   
   ==== Multi-master, multi-node, multi-az gossip-based cluster
  
positive.code: Create a Kubernetes cluster using the following command. This will create a cluster with a single master, multi-node and multi-az configuration:
  
      kops create cluster \
        --name cluster.k8s.local \
        --zones us-east-1d,us-east-1e \
        --state s3://kubernetes-aws-io \
        --yes
  
  The `create cluster` command only creates and stores the cluster config in the S3 bucket. Adding `--yes` option ensures that the cluster is immediately created as well.
  
  Alternatively, you may not specify the `--yes` option as part of the `kops create cluster` command. Then you can use `kops edit cluster cluster.k8s.local` command to view the current cluster state and make changes. The cluster creation, in that case, is started with the following command:
  
      kops update cluster cluster.k8s.local --yes
  
  The cluster can be verified as shown:
  
  ```
  $ kops validate cluster
  Using cluster from kubectl context: cluster.k8s.local
  
  Validating cluster cluster.k8s.local
  
  INSTANCE GROUPS
  NAME      ROLE  MACHINETYPE MIN MAX SUBNETS
  master-us-east-1d Master  m3.medium 1 1 us-east-1d
  nodes     Node  t2.medium 2 2 us-east-1d,us-east-1e
  
  NODE STATUS
  NAME        ROLE  READY
  
negative.code: ip-172-20-84-65.ec2.internal  node  True
  ip-172-20-93-167.ec2.internal master  True
  
  Your cluster example.cluster.k8s.local is ready
  ```
  
  Note that all masters are spread across different AZs.
  