kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fixing broken link 

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
This commit is contained in:
BrentDorsey 2017-04-17 17:14:38 -05:00 committed by Brent Dorsey
parent c34f77a916 80ea74842a
commit f5046600c3
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/labels.md
View File

@ -7,11 +7,10 @@ There are two main types of labels that kops can create:
Both are specified at the InstanceGroup level.
A nice use for CloudLabels is to specify [AWS cost allocation tags](http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html).
A nice use for cloudLabels is to specify [AWS cost allocation tags](http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html).
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.
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).
CloudLables and nodeLables are automatically applied to new nodes created by [AWS EC2 auto scaling groups](https://aws.amazon.com/autoscaling/).
An example:
@ -33,5 +32,9 @@ Note that keys and values are strings, so you need quotes around values that YAM
To apply changes, you'll need to do a `kops update cluster` and then likely a `kops rolling-update cluster`
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.
For AWS if `kops rolling-update cluster --instance-group nodes` returns "No rolling-update required." the
[kops rolling-update cluster](https://github.com/kubernetes/kops/blob/8bc48ef10a44a3e481b604f5dbb663420c68dcab/docs/cli/kops_rolling-update_cluster.md) `--force` flag can be used to force a rolling update, even when no changes are identified.
Example:
`kops rolling-update cluster --instance-group nodes --force`