anchor.diff:  
   === Creating a DNS-based Kubernetes cluster
   
  -To create a DNS-based Kubernetes cluster you'll need a top-level domain or subdomain that meet one of the following scenarios:
  +To create a DNS-based Kubernetes cluster you'll need a top-level domain or subdomain that meets one of the following scenarios:
   
   . Domain purchased/hosted via AWS
   . A subdomain under a domain purchased/hosted via AWS
   . Setting up Route53 for a domain purchased with another registrar, transfering the domain to Route53
   . Subdomain for clusters in Route53, leaving the domain at another registrar
   
  -Then you need to follow the instructions in https://github.com/kubernetes/kops/blob/master/docs/aws.md#configure-dns[configure DNS]. Typically, the first and the last bullet are common scenarios.
  -
  -==== Create private VPC
  +Then you need to follow the instructions in https://github.com/kubernetes/kops/blob/master/docs/aws.md#configure-dns[configure DNS]. Typically, the first and the last bullets are common scenarios.
  +
  +==== Create private hosted zone
   
   <to be fixed>
   TODO: What is the need for it?
  
positive.code: 
      kops create cluster \
        --dns private \
        --name cluster03.k8s-aws.internal \
        --zones us-east-1a,us-east-1b \
        --state s3://kubernetes-aws-config \
        --vpc $VPCID \
  
negative.code: 
  </to be fixed>
  
  === Creating a gossip-based Kubernetes cluster
  
  Kops also has experimental support for a gossip-based cluster. It uses Weave Mesh behind the scenes. This makes the process of creating a Kubernetes cluster using kops DNS-free, and much simpler. This also means a top-level domain or a subdomain is no longer required to create the cluster. To create a cluster using the gossip protocol, indicate this to Kops by using a cluster name with a suffix of `.k8s.local`.
  
  