Description of problem: The shared-resource-csi-driver-node in openshift-cluster-csi-drivers namespace does not define the resource requests for cpu/memory runs as “BestEffort” qosClass Version-Release number of selected component (if applicable): 4.10.0-0.nightly-2021-11-02-121455 How reproducible: Always Steps to Reproduce: 1. Set up Azure cluster 2. Install Azure-file CSI Driver with enable the feature gate 3. check shared-resource-csi-driver-node pod in openshift-cluster-csi-drivers namespace $ oc get pod shared-resource-csi-driver-node-4phdh -o json | jq .status.qosClass "BestEffort" Actual results: The shared-resource-csi-driver-node pod runs as “BestEffort” qosClass Expected results: We need to define the resource requests for cpu/memory in pod
All OCP components should have a better QOS class and CPU + memory requirements (copy from other drivers).
Verified the changes. $ oc get pod shared-resource-csi-driver-node-4w4wc -o json | jq .status.qosClass "Burstable" @jitsingh we are good to move the state to next level.
VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056