anchor.diff:        --master-zones $AWS_AVAILABILITY_ZONES \
         --node-count 5 \
         --zones $AWS_AVAILABILITY_ZONES \
  -      --state $KOPS_STATE_STORE \
         --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 servers across different AZs.
  
positive.code:     kops create cluster \
        --name example.cluster.k8s.local \
        --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.
  
negative.code: 
      kops delete cluster \
        <cluster-name> \
        --yes
  
  `<cluster-name>` is the name of the cluster. For example, our `example.cluster.k8s.local` cluster can be deleted as:
  
      kops delete cluster \
        example.cluster.k8s.local \
        --yes
  
  If you created a private VPC, then an additional cleanup of resources is required as shown below:
  