anchor.diff:  
   Alternatively, you can create a new cluster and use kops CLI options to specify the networking mode as shown below:
   
  -  export KOPS_STATE_STORE=s3://prefix-example-com-state-store
     kops create cluster \
       --name cluster2.k8s.local \
       --master-count 1 \
  
positive.code:     --networking calico \
      --yes
  
  This will create a 1 master node and 3 worker nodes cluster. It uses `--networking calico` which tells the cluster to use calico networking instead of the default networking provided by kubenet. Note, the name here is `cluster2.k8s.local` instead of the usual `cluster.k8s.local` name. This is just to make sure, in case, the two clusters can coexist.
  
  View the cluster configuration using the following command:
  
  
negative.code: 
    $ kubectl delete netpol deny-all-by-default --namespace=ns-1
    networkpolicy "deny-all-by-default" deleted
    $ kubectl create -f templates/allow-network-policy.yaml --namespace=ns-1
    networkpolicy "allow" created
  
  If we repeat the following command in `shell 2`, the call should still timeout and fail (again, you can press CTRL-C to quit after 10 seconds rather than waiting for the full timeout to occur):
  