Bug 2019722

Summary: The shared-resource-csi-driver-node pod runs as “BestEffort” qosClass
Product: OpenShift Container Platform Reporter: Wei Duan <wduan>
Component: BuildAssignee: Corey Daley <cdaley>
Status: CLOSED ERRATA QA Contact: Wei Duan <wduan>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.10CC: adam.kaplan, aos-bugs, jitsingh, jsafrane, pbhattac, pkumari, spandura, wking
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:24:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Wei Duan 2021-11-03 08:53:42 UTC 
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
Comment 1 Jan Safranek 2021-11-05 10:06:33 UTC 
All OCP components should have a better QOS class and CPU + memory requirements (copy from other drivers).
Comment 5 Priti Kumari 2021-12-07 10:20:43 UTC 
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.
Comment 6 Jitendar Singh 2021-12-07 10:22:32 UTC 
VERIFIED
Comment 9 errata-xmlrpc 2022-03-10 16:24:41 UTC 
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