From 85675ff19c4d134a3ea7aa3c2f4f92325e9efeec Mon Sep 17 00:00:00 2001 From: BrentDorsey Date: Mon, 17 Apr 2017 17:10:28 -0500 Subject: [PATCH] kops nodeLables - additional documentation to clarify how nodeLables work in AWS and a work around for kops rolling-update not recognizing any required changes in AWS. 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. --- docs/labels.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/labels.md b/docs/labels.md index 2319ad494d..c776de1d91 100644 --- a/docs/labels.md +++ b/docs/labels.md @@ -7,7 +7,12 @@ 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. An example: @@ -28,3 +33,6 @@ Note that keys and values are strings, so you need quotes around values that YAM would otherwise treat as numbers or booleans. 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. \ No newline at end of file