Skip to content

[Backport into 5.19] - Backporting into 5.19 #1611

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 18, 2025

Conversation

liranmauda
Copy link
Contributor

Explain the changes

  1. [Backport into 5.19] - Backporting into 5.19

dannyzaken and others added 2 commits May 18, 2025 13:01
- By default, enable the DB cluster monitoring in Prometheus
- A PodMonitor resource is created to scrape the DB pods
- The default metrics are defined in the config-map `cnpg-default-monitoring`
- The monitoring can be disabled by annotating noobaa CR with `noobaa.io/disable_db_default_monitoring=true`

Signed-off-by: Danny Zaken <[email protected]>
(cherry picked from commit c142d86)
- Devided the `run_ci` into 4 workflows
- Using native GH action minikube
- disabled the olm test as it is failing.

Signed-off-by: liranmauda <[email protected]>
(cherry picked from commit 755255f)
@liranmauda liranmauda merged commit 0443bd3 into noobaa:5.19 May 18, 2025
15 of 16 checks passed
@liranmauda liranmauda deleted the liran-backport-into-5.19 branch June 4, 2025 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants