Bug 1950035 - User workload Prometheus and Thanos ruler statefulsets should have 2 replicas and hard affinity set
Summary: User workload Prometheus and Thanos ruler statefulsets should have 2 replicas...
Keywords:
Status: CLOSED DUPLICATE of bug 1955490
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Damien Grisonnet
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-15 15:44 UTC by Simon Pasquier
Modified: 2021-04-30 12:05 UTC (History)
7 users (show)

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


Attachments (Terms of Use)

Description Simon Pasquier 2021-04-15 15:44:53 UTC
Description of problem:

As mentioned in the conventions doc https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#high-availability, both user-workload prometheus and thanos ruler should have a replica count of 2 with hard affinities set till we bring descheduler into our product.

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

How reproducible:
Always

Steps to Reproduce:
1. Enable user workload
2.
3.

Actual results:
prometheus-user-workload and thanos-ruler statefulsets use preferredDuringSchedulingIgnoredDuringExecution for node affinity.

Expected results:
they should use requiredDuringSchedulingIgnoredDuringExecution

Additional info:
Similar to bug 1949262 and bug 1948711


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