Description of problem: The vmware-vsphere-csi-driver-operator pod does not define the resource requests for cpu/memory,and runs as BestEffort qosClass. Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-04-05-174735 Steps to Reproduce: 1. Install vSphere cluster 2. Enable the TechPreviewNoUpgrade featureset 3. Check the vSphere csi driver operator pod $ oc -n openshift-cluster-csi-drivers get pod vmware-vsphere-csi-driver-operator-554d6dd6bb-vv5h7 -o json | jq .status.qosClass "BestEffort" Actual results: The vmware-vsphere-csi-driver-operator pod runs as BestEffort qosClass Expected results: We need to define the resource requests for cpu/memory for vmware-vsphere-csi-driver-operator pod.
Verified pass on 4.8.0-0.nightly-2021-04-18-101412. $ oc -n openshift-cluster-csi-drivers get pod -o json | jq -r '.items[].status.qosClass' Burstable Burstable Burstable Burstable Burstable Burstable Burstable
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.8.2 bug fix and 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-2021:2438