Undefined Description of problem:
CSI pods have priority 0 instead of using openshift priorityclasses (https://docs.openshift.com/container-platform/4.13/nodes/pods/nodes-pods-priority.html). Customer workloads also have priority 0 by default, which leads to a race for scheduling and resources.
Version-Release number of selected component (if applicable):
Not sure
How reproducible:
This was triggered via a DR testing scenario. So I think trying to quickly spin up full workloads on an empty cluster
Steps to Reproduce:
1. Apply CSI pods and customer workloads at the same time 2. Repeat until race is hit where CSI pods cannot be scheduled.
Actual results:
CSI pods can't be scheduled when customer workloads get there first
Expected results:
CSI pods are scheduled before customer workloads
Additional info:
