anchor.diff:  
   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:
  +applied to the instances in the instance group - we'll need the label to schedule pods onto these instances:
   
   ```
   $ kubectl get nodes -l type=p2-ig
  
positive.code: In this section you'll add an additional instance group to your Kubernetes cluster so that your cluster is
  comprised of two instance groups with different instance types. We'll then schedule a pod to run specifically
  on instances in the new instance group. This is useful, for example, if you want to assign pods to run high performing workloads
  on GPU or FPGA instance types.
  
  Let's go ahead and create an instance group for p2 instance types:
  
      kops create ig p2 --subnet us-east-1d,us-east-1e
  
  Change the machineType in the resulting skeleton configuration. Make sure you add the nodeLabels as in the example below.
  This will be used in a later example to schedule pods onto these instances.
  
  ```
  
negative.code: .
  Will modify resources:
    LaunchConfiguration/nodes.cluster.k8s.local
    	InstanceType        	 t2.medium -> m4.large
  
  Must specify --yes to apply changes
  ```
  