You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-node/2902-cpumanager-distribute-cpus-policy-option/README.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -221,7 +221,8 @@ No changes. Existing container will not see their allocation changed. New contai
221
221
222
222
###### What specific metrics should inform a rollback?
223
223
224
-
Not Applicable.
224
+
As part of graduation of this feature, we plan to add metric `cpu_manager_numa_allocation_spread` to see how the CPUs are distributed across NUMA nodes.
225
+
This can be used to see the CPU distribution across NUMA and will provide an indication of a rollback.
225
226
226
227
###### Were upgrade and rollback tested? Was the upgrade->downgrade->upgrade path tested?
227
228
@@ -238,6 +239,8 @@ No
238
239
239
240
Inspect the kubelet configuration of a node -- check for the presence of the feature gate and usage of the new policy option.
240
241
242
+
In addition to that, we can check the metric `cpu_manager_numa_allocation_spread` to determine how allocated CPUs are spread across NUMA node.
243
+
241
244
###### How can someone using this feature know that it is working for their instance?
242
245
243
246
In order to verify this feature is working, one should:
@@ -251,6 +254,8 @@ To verify the list of CPUs allocated to the container, one can either:
251
254
-`exec` into uthe container and run `taskset -cp 1` (assuming this command is available in the container).
252
255
- Call the `GetCPUS()` method of the `CPUProvider` interface in the `kubelet`'s [podresources API](https://pkg.go.dev/k8s.io/kubernetes/pkg/kubelet/apis/podresources#CPUsProvider).
253
256
257
+
Also, we can check `cpu_manager_numa_allocation_spread` metric.
258
+
254
259
###### What are the reasonable SLOs (Service Level Objectives) for the enhancement?
255
260
256
261
There are no specific SLOs for this feature.
@@ -262,7 +267,8 @@ None
262
267
263
268
###### Are there any missing metrics that would be useful to have to improve observability of this feature?
264
269
265
-
None
270
+
Yes, as part of graduation of this feature to Beta, we plan to add `cpu_manager_numa_allocation_spread` metric
271
+
to provide data on how the CPUs are distributed across NUMA nodes.
266
272
267
273
###### Does this feature depend on any specific services running in the cluster?
0 commit comments