anchor.diff:  
   == Install kops
   
  -There is no need to download the Kubernetes binary distribution for creating a cluster using kops. However, you do need to download the kops CLI. It then takes care of downloading the right Kubernetes binary in the cloud, and provisions the cluster.
  +There is no need to download a Kubernetes binary distribution for creating a cluster using kops. However, you do need to download the kops CLI. It then takes care of downloading the right Kubernetes binary in the cloud, and provisions the cluster.
   
       brew update && brew install kops
   
  
positive.code: - Setting up AWS resources such as networks, Auto Scaling groups, IAM users, and security groups
  - Installing Kubernetes.
  
  Create a simple Kubernetes cluster using the following command. The cluster name suffix of `.k8s.local` will result in the gossip protocol being used for master/node discovery. Note that `create cluster` only creates and stores the cluster config in S3; you must use `update cluster` to build the cluster:
  
      kops create cluster \
        --name cluster01.k8s.local \
        --zones us-east-1d,us-east-1e \
        --state s3://kubernetes-aws-config
      # review cluster info and make changes if necessary (for ex, subnet sizing)
      kops get cluster
      kops edit cluster cluster01.kubernetes-aws.k8s.local
      # update and commit
      kops update cluster cluster01.kubernetes-aws.k8s.local --yes
  
  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 \
        --master-count 3 \
        --master-zones us-east-1a,us-east-1b \
        --node-count 5 \
        --zones us-east-1a,us-east-1b,us-east-1c \
        --state s3://kubernetes-aws-config
  
  Create a cluster with Route53 private hosted zone and VPC. For this to work you must have created the Route53 private hosted zone, as explained in <<Create hosted zone on Route53>>:
  
  
negative.code:       --network-cidr 10.1.0.0/16 \
        --ssh-public-key $mypubkey
  
  TIP: You may need to add cluster API endpoints into your hosts file (/etc/hosts) if you use Route53
  private hosted zone along with VPC option.
  
  == Delete cluster
  
  Any cluster can be deleted as shown:
  
      kops delete cluster \
        <cluster-name> \
        --state s3://kubernetes-aws-io \
        --yes
  
  `<cluster-name>` is the name of the cluster. For example, our `cluster.k8s.local` cluster can be deleted as:
  
      kops delete cluster \
        cluster.k8s.local \
        --state s3://kubernetes-aws-io \
        --yes
  
  
  If you created a private VPC, then an additional cleanup of resources is required as shown below:
  
      # Find Route53 hosted zone ID from the console or via CLI and delete hosted zone
      aws route53 delete-hosted-zone --id Z1234567890ABC
      # Delete VPC if you created earlier
  