We are expecting a non-negligible amount of Pods to be created in the mediawiki-dumps-legacy namespace when the dumps are running.
Granted, this will be limited by the parallelism of the dumps pools themselves, but we should make sure that Pods are not failing to be created because we are maxing out the allotted namespace resources defined in its associated LimitRange.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| data-platform: monitor namespace resource quota usage over time | operations/alerts | master | +320 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T88728 Improve Wikimedia dumping infrastructure | |||
| Resolved | BTullis | T352650 WE 5.4 KR - Hypothesis 5.4.4 - Q3 FY24/25 - Migrate current-generation dumps to run on kubernetes | |||
| Resolved | brouberol | T388378 Orchestrate dumps v1 from an airflow instance | |||
| Resolved | brouberol | T389777 Monitor the resource usage in the mediawiki-dumps-legacy namespace |
Change #1138346 had a related patch set uploaded (by Brouberol; author: Brouberol):
[operations/alerts@master] data-platform: monitor namespace resource quota usage over time
We've created monitors that will cover all namespaces. not just mediawiki-dumps-legacym so that everyone benefits from that work.
Change #1138346 merged by Brouberol:
[operations/alerts@master] data-platform: monitor namespace resource quota usage over time