anchor.diff:        Status=Enabled
       export KOPS_STATE_STORE=s3://kubernetes-aws-config
   
  -== Create hosted zone on Route53 (optional)
  +== Create hosted zone on Route53
   
  -As of Kops 1.6.2, a top-level domain or a subdomain is no longer required to create the cluster. Instead, a gossip-based cluster can be easily created. The only requirement to trigger this is to have the cluster name end with `.k8s.local`. If you wish to use a gossip-based cluster, then you can skip this section.
  +DNS is used by Kubernetes to allow the various Kubernetes components to find and communicate with each other.
  +
  +As an alternative to using DNS, Kops 1.6.2 introduced the ability to create a gossip-based cluster, making a top-level domain or a subdomain no longer required to create the cluster. The only requirement to trigger this is to have the cluster name end with `.k8s.local`. This is a fairly recent feature, so we recommend you continue to use DNS for production clusters. If you wish to use a gossip-based cluster, then you can skip this section.
   
   The domain allows the worker nodes to discover the master and the master to discover all the etcd servers. This is also needed for kubectl to be able to talk directly with the master.
   
  
positive.code:       --zones us-east-1a,us-east-1b,us-east-1c \
        --state s3://kubernetes-aws-config
  
  Create cluster with Route53 private hosted zone and VPC
  
      kops create cluster \
        --dns private \
  
negative.code: 
  More options for creating k8s clusters are listed below.
  
  Create a cluster with multi master, multi node and multi-az configuration. As with the example above, this will create a cluster using the gossip protocol:
  
      kops create cluster \
        --name cluster02.k8s.local \
  