anchor.diff:  ```
   
   We expect kops to have created a new LaunchConfiguration using our updated EC2 instance type and updated our
  -ASG to refer to this LaunchConfiguration, so let's check if this is indeed the case:
  +ASG to refer to this LaunchConfiguration, so let's check if this is indeed the case. Note that the name of the
  +LaunchConfiguration associated with the ASG has changed, and the LaunchConfiguration reflects the new instance type:
   
   ```
   $ aws autoscaling describe-auto-scaling-groups --auto-scaling-group-names nodes.cluster.k8s.local --query 'AutoScalingGroups[0].[LaunchConfigurationName]'
  
positive.code: 
  If you have a lot of instances in your cluster, you can show only the instances in your new instance group using the
  label we assigned during the creation of the instance group earlier. This also confirms that the label has been
  applied to the instances in the instance group - we'll need this to schedule pods onto these instances:
  
  ```
  $ kubectl get nodes -l type=p2-ig
  
negative.code: Using cluster from kubectl context: cluster.k8s.local
  
  NAME			    STATUS		NEEDUPDATE	READY	MIN	MAX	NODES
  master-us-east-1d   Ready		0		    1	    1	1	1
  nodes			    NeedsUpdate	2		    0	    2	8	2
  
  Must specify --yes to rolling-update.
  