Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

priority expander: Documentation updates #2433

Merged
merged 3 commits into from
Oct 11, 2019
Merged

priority expander: Documentation updates #2433

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f671478
priority expander: Document random fallback
mgalgs Oct 9, 2019
2e0d1f0
priority expander: Use kube-system namespace in example
mgalgs Oct 9, 2019
0b7429a
priority expander: Document skipping behavior for unmatched groups
mgalgs Oct 9, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion cluster-autoscaler/expander/priority/readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ apiVersion: v1
kind: ConfigMap
metadata:
name: cluster-autoscaler-priority-expander
namespace: kube-system
data:
priorities: |-
10:
Expand All @@ -29,6 +30,8 @@ data:
- .*m4\.4xlarge.*
```

The priority should be a positive value. The highest value wins. For each priority value, a list of regular expressions should be given. If there are multiple node groups matching any of the regular expressions with the highest priority, one group to expand the cluster is selected each time at random. Priority values cannot be duplicated - in that case, only one of the lists will be used.
The priority should be a positive value. The highest value wins. For each priority value, a list of regular expressions should be given. If there are multiple node groups matching any of the regular expressions with the highest priority, one group to expand the cluster is selected each time at random. Priority values cannot be duplicated - in that case, only one of the lists will be used. If no match is found, a group will be selected at random.

Note that if a group name doesn't match any of the regular expressions in the priority list it will not be considered for expansion. To ensure that *all* of your groups are autoscaled you might want to add a "catch-all" regex of `.*` (with a low priority) to your priorities list.

In the example above, the user gives the highest priority to any expansion option, where the scaling group ID matches the regular expression `.*m4\.4xlarge.*`. Assuming all of the used scaling groups are based on AWS Spot instances, the user might now want to give up on all the scaling groups based on the `m4.4xlarge` instance family. To do that, it's enough to either reconfigure the priority to a value `<10` or remove the entry with priority `50` altogether.