-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
CNF Compute Sprint 274, CNF Compute Sprint 275, CNF Compute Sprint 276, CNF Compute Sprint 277
-
4
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When doing any changes to the performance profile through management cluster's config map sometimes after the nodepool got updated the kubeletconfig map doesn't get updated to the latest changes.
Version-Release number of selected component (if applicable):
How reproducible:
Sometimes
Steps to Reproduce:
1. Apply a performance profile config map and attach it to the nodepool
2. Edit the performance profile config map and add annotations to it under the metadata:
annotations:
kubeletconfig.experimental: |
{"topologyManagerScope": "container",
"cpuManagerPolicyOptions": {"full-pcpus-only": "false"}
}
3. Wait for the nodepool to finish updating after the changes
4. See if the changes took place
Actual results:
Expected results:
Additional info: