anchor.diff:  
   Once the `kops create cluster` command is issued, it provisions the EC2 instances, setup Auto Scaling Groups, IAM users, security groups, and install Kubernetes on each node, configures master and worker nodes. This process can take a few minutes based upon the number of master and worker nodes.
   
  -Wait for 10-15 minutes and then the cluster can be validated as shown:
  +Wait for 5-8 minutes and then the cluster can be validated as shown:
   
   ```
   $ kops validate cluster --name=example.cluster.com
  
positive.code: 
  `--zones` option is also used to distribute the worker nodes. The number of workers is specified using the `--node-count` option.
  
  As mentioned above, wait for 10-15 minutes for the cluster to be created. Validate the cluster:
  
  ```
  $ kops validate cluster --name=example.cluster.com
  
negative.code: 
  Although most of the exercises in this workshop should work on a cluster with a private VPC, some commands won't, specifically those that use a proxy to access internally hosted services.
  
  == Kubernetes Cluster Context
  
  You may create multiple Kubernetes clusters. The configuration for each cluster is stored in a configuration file, referred to as "`kubeconfig file`". By default, kubectl looks for a file named `config` in the directory `~/.kube`. The kubectl CLI uses kubeconfig file to find the information it needs to choose a cluster and communicate with the API server of a cluster.
  