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.

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

Allow static cpu manager policy to be enabled on nodepools #2446

Merged
merged 1 commit into from
Aug 26, 2019

Conversation

arjunrn
Copy link
Contributor

@arjunrn arjunrn commented Aug 23, 2019

The static CPU management policies allow entire CPUs to be allocated to pods which might be useful for workloads which benefit from CPU affinity. The static policy is only enabled when the config item is present and static to the value static.

@@ -69,6 +69,8 @@ clusters:
profile: ${WORKER_PROFILE}-splitaz
min_size: 3
max_size: 21
config_items:
cpu_manager_policy: static
- discount_strategy: spot_max_price
instance_types: ["m4.large", "m5.large", "m5.xlarge", "m4.xlarge"]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it mean that the cpu_manager_policy can be set only in the node pools with these type of instances?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, those are just our end to end tests where we create nodepools.

@arjunrn arjunrn force-pushed the static-cpu-manager branch from 41b05d0 to 9e7a63c Compare August 23, 2019 15:45
@mikkeloscar
Copy link
Contributor

👍

@@ -69,6 +69,8 @@ clusters:
profile: ${WORKER_PROFILE}-splitaz
min_size: 3
max_size: 21
config_items:
cpu_manager_policy: static
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wrong name: cpu_manager_policy != cpu_management_policy

@@ -52,6 +52,9 @@ write_files:
featureGates:
SupportPodPidsLimit: true
podPidsLimit: {{ .NodePool.ConfigItems.pod_max_pids }}
{{- end }}
{{- if eq .NodePool.ConfigItems.cpu_management_policy "static" }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there more resonable options? If yes it would make sense to do:

{{- if ... }}
  cpuManagerPolicy: {{ .NodePool.ConfigItems.cpu_management_policy }}
{{- end }}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or even drop the if if you have a default.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's only none and static, but it might make sense to just drop the if since we are going to roll the nodes for v1.14 anyway, so the if doesn't provide so much in this case :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have dropped the if and used the same keyword everywhere.

@arjunrn arjunrn force-pushed the static-cpu-manager branch from 9e7a63c to 5e1a63b Compare August 26, 2019 09:37
@arjunrn arjunrn force-pushed the static-cpu-manager branch from 5e1a63b to 9fd5a1a Compare August 26, 2019 10:09
@mikkeloscar
Copy link
Contributor

👍

1 similar comment
@gargravarr
Copy link
Contributor

👍

@gargravarr gargravarr merged commit eddb43b into dev Aug 26, 2019
@gargravarr gargravarr deleted the static-cpu-manager branch August 26, 2019 11:50
This was referenced Aug 26, 2019
This was referenced Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants