Bug 1945856 - Setup different priority classes for prometheus-k8s and prometheus-user-workload pods
Summary: Setup different priority classes for prometheus-k8s and prometheus-user-workl...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: Simon Pasquier
QA Contact: Junqi Zhao
Depends On: 1934516
TreeView+ depends on / blocked
Reported: 2021-04-02 09:37 UTC by Simon Pasquier
Modified: 2021-05-04 19:51 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1934516
Last Closed: 2021-05-04 19:50:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 1103 0 None open Bug 1945856: Revert "Bug 1934516: [4.7]: jsonnet/prometheus.jsonnet: Apply system-cluster-critical class to cluster Prom... 2021-04-14 13:22:15 UTC
Github openshift kubernetes pull 642 0 None open Bug 1945856: 99729:Only system-node-critical pods should be OOM Killed last 2021-04-15 01:00:56 UTC
Red Hat Product Errata RHBA-2021:1365 0 None None None 2021-05-04 19:51:14 UTC

Comment 5 errata-xmlrpc 2021-05-04 19:50:50 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 (OpenShift Container Platform 4.7.9 bug fix 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.


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