[Feature] Prometheus alerts installed by operator chart

[maxemann96]

Following up the comment from @itay-grudev, I now create a new issue, as I didn't found any other issue describing my feature request.

Automated alerts for cluster issues would be extremely useful to improve the safety of a CNPG cluster.

Currently I'm using the following workaround:

curl https://raw.githubusercontent.com/cloudnative-pg/cloudnative-pg/main/docs/src/samples/monitoring/prometheusrule.yaml | kubectl -n NAMESPACE apply -f -

Also related to #100

Side note: This is a duplicate of #452. Since there was never an answer and the stale bot just closed it, I'm now opening a new issue. I'm happy to get an answer of a non bot (even if it is the same, i. e. "Not planned"). Thanks in advance :)

[dosubot]

Hi, @maxemann96. I'm Dosu, and I'm helping the charts team manage their backlog and am marking this issue as stale.

Issue Summary:

• You requested the operator chart to automatically install Prometheus alerts for cluster issues to enhance CNPG cluster safety.
• Currently, you use a manual PrometheusRule YAML workaround.
• You noted this issue duplicates a previously closed one that received no response.
• You are seeking clarity on whether this feature is planned.
• No comments or updates have been made on this issue so far.

Next Steps:

• Please let me know if this feature request is still relevant to the latest version of the charts by commenting on this issue.
• If I do not hear back within 7 days, I will automatically close this issue.

Thank you for your understanding and contribution!

[maxemann96]

Still relevant

[dosubot]

Hi @maxemann96, thanks for confirming this is still relevant. @sxd, could you please assist with this feature request regarding automatic Prometheus alerts in the operator chart?

[jameshearttech]

@maxemann96 I'm looking into creating PrometheusRule resources and came across this issue. I read through #100 and #452 as well. I saw the comment that the cluster chart creates PrometheusRule resources, which makes sense I guess because they could vary (e.g., thresholds).

[maxemann96]

Hi @jameshearttech, I think configuring the rules via an optional helm chart flag (like monitoring.prometheusRule.enabled) and the possibility to directly configure these rules (like monitoring.prometheusRule.rules) with the default of the sample rules would be a nice addition to the operator chart.

[dosubot]

Hi, @maxemann96. I'm Dosu, and I'm helping the charts team manage their backlog and am marking this issue as stale.

Issue Summary:

• You requested a feature for the operator chart to automatically install Prometheus alerts for cluster issues, which currently requires manual PrometheusRule YAML management.
• The issue was previously marked stale but you confirmed it remains relevant.
• There has been discussion about adding helm chart flags to enable and configure Prometheus rules directly in the operator chart.
• Other users have shown interest in creating PrometheusRule resources and referenced related issues.
• Maintainers have been asked for input on this feature request.

Next Steps:

• Please let me know if this feature is still important for your use case with the latest version of the charts by commenting on this issue.
• If I do not hear back within 7 days, I will automatically close this issue to keep the backlog manageable.

Thank you for your understanding and contribution!

[maxemann96]

Still relevant

[dosubot]

Hi, @maxemann96. I'm Dosu, and I'm helping the charts team manage their backlog and am marking this issue as stale.

Issue Summary

• You requested that the operator chart automatically install Prometheus alert rules so users do not need to manually apply the sample prometheusrule.yaml.
• The goal was to improve CNPG cluster safety by making the alerting setup easier to adopt.
• The issue was marked stale twice, and each time you confirmed that it is still relevant.
• In the discussion, related issues were referenced and there was some agreement that PrometheusRule resources may fit better in the cluster chart, with optional Helm configuration suggested as a possible approach.
• No final resolution or implementation decision has been posted yet.

Next Steps

• Please let us know if this is still relevant with the latest version of the charts repository.
• If it is still relevant, you can keep the discussion open by commenting on the issue; otherwise, it will be automatically closed in 7 days.

Thanks for your understanding and contribution.

[maxemann96]

Aaaaaand another uselss "Not stale" comment. See https://nostalebots.xyz/. K8s Projekt also reconfigured stale bot.