anchor.diff:  Validate the cluster:
   
   ```
  -$ kops validate cluster --name=cluster.kubernetes-aws.io
  -Validating cluster cluster.kubernetes-aws.io
  +$ kops validate cluster --name=$KOPS_CLUSTER_NAME
  +Validating cluster example.cluster.com
   
   INSTANCE GROUPS
   NAME      ROLE  MACHINETYPE MIN MAX SUBNETS
  
positive.code: one step by passing the `--yes` flag.
  
      kops create cluster \
        --name cluster.kubernetes-aws.io \
        --master-count 3 \
        --master-zones us-east-1a,us-east-1b,us-east-1c \
        --node-count 5 \
        --zones us-east-1a,us-east-1b,us-east-1c \
        --state s3://kubernetes-aws-io \
        --yes
  
  A multi-master cluster can be created by using the `--master-count` option and using an odd number value. The AZs for master can be specified using the `--master-zones` option. Kops will spread the nodes across different AZs.
  
negative.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 $KOPS_CLUSTER_NAME \
        --zones $AWS_AVAILABILITY_ZONES \
        --state $KOPS_STATE_STORE \
        --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 $KOPS_CLUSTER_NAME --yes
  
  The cluster can be verified as shown:
  
  ```
  $ kops validate cluster --name=$KOPS_CLUSTER_NAME
  Validating cluster example.cluster.com
  
  INSTANCE GROUPS
  NAME      ROLE  MACHINETYPE MIN MAX SUBNETS
  