XML

Word

Printable

Epic Name:
resource limits
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Not Selected
Docs QE Status:
NEW
Epic Status:
To Do
Parent Link:
MON-3159Technical Debt
QE Status:
NEW
Hierarchy Progress:
100
Hierarchy Progress Bar:

100% 100%
Release Note Text:

Hide
With this release, you can now specify resource requests and limits for all monitoring components, including the following:

* Alertmanager
* kube-state-metrics
* node-exporter
* openshift-state-metrics
* Prometheus
* Prometheus Operator and its Admission webhook
* Telemeter Client
* Thanos Querier
* Thanos Ruler

In previous versions of {product-title}, you could only set options for Prometheus, Alertmanager, Thanos Querier, and Thanos Ruler.

Show
With this release, you can now specify resource requests and limits for all monitoring components, including the following: * Alertmanager * kube-state-metrics * node-exporter * openshift-state-metrics * Prometheus * Prometheus Operator and its Admission webhook * Telemeter Client * Thanos Querier * Thanos Ruler In previous versions of {product-title}, you could only set options for Prometheus, Alertmanager, Thanos Querier, and Thanos Ruler.
Release Note Type:
Enhancement
Target Version:

openshift-4.14

Epic Goal

Users can today specify resource requirements for some of the components:
- Prometheus (in-cluster and UWM), only for the prometheus container.
- Alertmanager (in-cluster and UWM), only for the alertmanager container.
- Thanos Querier, only for the thanos-query container.
- Thanos Ruler, only for the thanos-ruler container.
We should extend that too all containers, that potentially use too many resources.
Similar configuration options might be exposed for other components (subject for evaluation)

Why is this important?

The current set of resource limitations is not sufficient. https://issues.redhat.com/browse/OCPBUGS-12714 shows a case where node-exporter could have benefited from this.

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
...

CI - CI is running, tests are automated and merged.
Release Enablement <link to Feature Enablement Presentation>
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Polarion: <link or reference to Polarion>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>

is related to

MON-3260 Make node_exporter aware of k8s cpu limits

links to