anchor.diff:  
       $ kops get ig
       Using cluster from kubectl context: cluster.k8s.local
  -
       NAME			    ROLE	MACHINETYPE	MIN	MAX	SUBNETS
  -    master-us-east-1d	Master	m3.medium	1	1	us-east-1d
  +    master-us-east-1d   Master	m3.medium	1	1	us-east-1d
       nodes			    Node	m4.large	2	8	us-east-1d,us-east-1e
   
   However, the EC2 instances running as worker nodes in the Kubernetes cluster have not yet been updated. You can check
  
positive.code: An instance group is a kops concept that defines a grouping of similar machines. In AWS, an instance group maps to an
  AutoScalingGroup (ASG).
  
  In this section we'll look at different ways of using kops instance groups in a Kubernetes cluster:
  
  . Update the instance group by adjusting its size, or the instance types it contains
  . Add an additional instance group to a cluster, and schedule pods on the instances in the new instance group
  . Pin an instance group pinned to a specific AZ
  
  == Basic instance group commands
  
  List the instance groups in your cluster:
  
      kops get ig
  
    $ kops get ig
      Using cluster from kubectl context: cluster.k8s.local
  
      NAME			    ROLE	MACHINETYPE	MIN	MAX	SUBNETS
      master-us-east-1d	Master	m3.medium	1	1	us-east-1d
      nodes			    Node	t2.medium	2	6	us-east-1d,us-east-1e
  
negative.code: 
  After applying the changes it will take a few minutes before your ASG provisions the instances and reaches the MinSize
  specified in the instance group config. You can check progress by viewing the nodes in your cluster. AWS may only
  provision one P2 instance instead of the two specified; this is because most AWS accounts have
  a soft limit of 1 P2 instance per account. If this happens, don't worry, we can still provision pods onto the P2 instance(s) in
  this instance group.
  
  Check that your new instances have been provsioned:
  
  ```
  $ kubectl get nodes
  