forked from kubernetes/kops
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix kubernetes#441 Fix kubernetes#241 Issue kubernetes#311
- Loading branch information
Showing
1 changed file
with
29 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
# Labels | ||
|
||
There are two main types of labels that kops can create: | ||
|
||
* `CloudLabels` become tags in AWS on the instances | ||
* `NodeLabels` become labels on the k8s Node objects | ||
|
||
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) | ||
|
||
An example: | ||
|
||
`kops edit ig nodes` | ||
|
||
``` | ||
... | ||
nodeLabels: | ||
spot: "false" | ||
cloudLabels: | ||
team: me | ||
project: ion | ||
... | ||
``` | ||
|
||
Note that keys and values are strings, so you need quotes around values that YAML | ||
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` |