Bug 1953479 - New OCP priority classes are not used - Virt
Summary: New OCP priority classes are not used - Virt
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 2.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.9.0
Assignee: aschuett
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-26 08:32 UTC by Fabian Deutsch
Modified: 2021-06-30 12:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-30 12:23:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Fabian Deutsch 2021-04-26 08:32:22 UTC
Description of problem:
OCP has changed hte names of priority classes. This component's _infrastructure pods_ classes should be added or adjusted accordingly to either system-cluster-critical or system-node-critical priority.

See https://mailman-int.corp.redhat.com/archives/aos-devel/2021-April/msg00402.html

The new classes must not be set on user workloads (i.e. VMs)

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Infrastructure components should carry the new priority classes


Additional info:

Comment 4 sgott 2021-06-30 12:23:09 UTC
We already use the highest priority values that are safe to use. If we raised them, we could compete with node level infrastructure that KubeVirt depends on to run.

Because we have not seen complaints that our current priority classes are an issue, we're opting not to change current values for now.


Note You need to log in before you can comment on or make changes to this bug.