adjusting wording to clarify both cloudLables and nodeLables are automatically applied to new nodes create by AWS EC2 auto scaling groups.
adding --force flag example
A good use for nodeLables is to implement [nodeSelector labels](https://kubernetes
.io/docs/concepts/configuration/assign-pod-node/#step-two-add-a-nodeselector-field-to-your-pod-configuration) that survive
[AWS EC2 auto scaling groups](https://aws.amazon.com/autoscaling/) replacing unhealthy or unreachable instances.
Note for AWS if `kops rolling-update cluster --instance-group nodes` returns "No rolling-update required." you'll need to
manually terminate the EC2 node for the auto scaling group to propagate the new labels.
A good use for nodeLables is to implement [nodeSelector labels](https://kubernetes
.io/docs/concepts/configuration/assign-pod-node/#step-two-add-a-nodeselector-field-to-your-pod-configuration) that survive
[AWS EC2 auto scaling groups](https://aws.amazon.com/autoscaling/) replacing unhealthy or unreachable instances.
Note for AWS if `kops rolling-update cluster --instance-group nodes` returns "No rolling-update required." you'll need to
manually terminate the EC2 node for the auto scaling group to propagate the new labels.
A good use for nodeLables is to implement [nodeSelector labels](https://kubernetes
.io/docs/concepts/configuration/assign-pod-node/#step-two-add-a-nodeselector-field-to-your-pod-configuration) that survive
[AWS EC2 auto scaling groups](https://aws.amazon.com/autoscaling/) replacing unhealthy or unreachable instances.
Note for AWS if `kops rolling-update cluster --instance-group nodes` returns "No rolling-update required." you'll need to
manually terminate the EC2 node for the auto scaling group to propagate the new labels.
BrentDorsey