-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.17.z, 4.16.z, 4.18
-
None
-
False
-
-
Description of problem:
It is not possible to configure autoSizingReserved: true via a PerformanceProfile and have it reflected in the KubeletConfig generated from that PerformanceProfile. This prevents customers from using the Automatically allocating resources for nodes feature[1] of OpenShift in combination with a PerformanceProfile because only a single KubeletConfig is applied/supported. The PerformanceProfile can contain a kubeletconfig.experimental annotation that added the contents of that annotation to KubeletConfig.spec.kubeletConfig, however autoSizingReserved needs to be declared at the parent level, i.e. KubeletConfig.spec.autoSizingReserved (not KubeletConfig.spec.kubeletConfig.autoSizingReserved) Related slack discussion: https://redhat-internal.slack.com/archives/CQNBUEVM2/p1739565760777209 [1] https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/nodes/working-with-nodes#nodes-nodes-resources-configuring-auto_nodes-nodes-resources-configuring
Version-Release number of selected component (if applicable):
All versions
How reproducible:
100%
Steps to Reproduce:
1. create a PerformanceProfile with metatadat.annotations.kubeletconfig.experimental: "autoSizingReserved: true" 2. Apply PerformanceProfile 3. Retrieve KubeletConfig. The KubeletConfig.spec.autoSizingReserved property is not present under KubeletConfig.spec.
Actual results:
The KubeletConfig.spec.autoSizingReserved property is not present under KubeletConfig.spec
Expected results:
The KubeletConfig.spec.autoSizingReserved property should be present under KubeletConfig.spec
Additional info:
Related slack discussion: https://redhat-internal.slack.com/archives/CQNBUEVM2/p1739565760777209
- is blocked by
-
OCPBUGS-41857 perfomance profile overrides systemReserved memory set by autosizing
-
- ASSIGNED
-