Bug 2232582 - CSI pods and customer workloads both have 'priority=0' and race for resources
Summary: CSI pods and customer workloads both have 'priority=0' and race for resources
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-managed-service
Version: 4.11
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ohad
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-17 13:21 UTC by Florian Bergmann
Modified: 2023-08-17 14:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Florian Bergmann 2023-08-17 13:21:15 UTC 
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. It requires workloads that exhaust the resources of a node, so the CSI pods that get scheduled will no longer be place-able on a node.

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:
Note You need to log in before you can comment on or make changes to this bug.