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

Merge pull request #224 from mwielgus/nap-prop-fix 

Labels in NAP proposal update
This commit is contained in:
Marcin Wielgus 2017-08-16 17:58:45 +05:30 committed by GitHub
parent 111eb1d797 f6a7eadadf
commit ca5f3b7424
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
cluster-autoscaler/proposals/node_autoprovisioning.md
View File

@ -98,14 +98,15 @@ Then we calculate the stats of all node selectors of the pods. For each signific
Example: Example:
* `S1: x in (“a”, “b”,”c”) and y not in (“z”)` * `S1: x = "a" and machine_type="n1-standard-2"
* `S2: x in (“b”, “d”) and y in (“m”)` * `S2: y = "b"
* `S3: x notexists` * `S3: x = "c"
* `S4: y exists` * `S4: machine_type = "n1-standard-16"
S1 is compatible with S2 and S4. S2 is compatible with S1 and S4. S3 is compatible with S4. S1 is compatible with S2 and S4. S2 is compatible with S1, S3 and S4. S3 is compatible with S4 and S2.
The label selector that would come from S1, S2 and S4 would be x in (“b”, “d”) and y in (“m”). If multiple options are allowed for a single label then the most popular value for the label wins (in the existing nodes), in case of tie - the lexicographically smaller. So for S1, S2 and S4 it would be x = “b” and y = “m” (assuming that there are no nodes with x). The label selector that would come from S1, S2 and S4 would be x="a" and y="b" and machine_type = "n1-standard-2", however
depending on popularity, the other option is S2, S3, S4 => x="c", y="b" and machine_type = "n1-standard-16".
# Testing # Testing