Cluster Chart: Prometheus rule expressions are not cluster specific

[fpfuetsch]

Currently the prometheus rule expressions do not specify a specific cluster but only a specific namespace. This causes duplicated alerts if multiple clusters are deployed (with their own prom rules) in the same namespace, since in those cases the prom rules of the other clusters fire as well.

To solve this the prometheus rule expressions should not filter for a namespace but for the metrics of a specific cluster using the job attribute of the metrics.

[dosubot]

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

Issue Summary

• The issue highlights that Prometheus rule expressions are filtering by namespace instead of by cluster.
• This misconfiguration leads to duplicated alerts when multiple clusters share a namespace.
• The proposed solution is to adjust the rule expressions to filter using the job attribute.
• There have been no further comments or updates on this issue.

Next Steps

• Could you confirm if this issue is still relevant to the latest version of the charts repository? If so, please comment to keep the discussion open.
• If there are no updates, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

[fpfuetsch]

This issue is still present in the lastest version of the chart.

[dosubot]

@ sxd, the user has indicated that the issue regarding Prometheus rule expressions filtering by namespace is still relevant. Could you please assist them with this?

[fpfuetsch]

Still relevant, reopen please.

[dosubot]

@sxd The user has indicated that the issue is still relevant and requests it to be reopened. Could you please take a look and assist?