Skip to content
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

[kube-prometheus-stack] multi tenant alert routing #1274

Conversation

nrobert13
Copy link

Signed-off-by: Robert N [email protected]

What this PR does / why we need it:

allow alert routing in multi tenant clusters to different teams

Which issue this PR fixes

(optional, in fixes #<issue_number> (, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

Special notes for your reviewer:

hey @vsliouniaev , @bismarck, @gianrubio , @gkarthiks, @scottrigby, @Xtigyro, would you be so kind to review this change. Thanks in advance.
Cheers,
Robert

Checklist

  • DCO signed
  • Chart Version bumped
  • Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

Signed-off-by: Robert N <[email protected]>
Signed-off-by: Robert Nemeti <[email protected]>
@@ -18,7 +18,7 @@ name: kube-prometheus-stack
sources:
- https://github.com/prometheus-community/helm-charts
- https://github.com/prometheus-operator/kube-prometheus
version: 18.0.0
version: 18.0.2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adding new feature should raise chart minor version

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@monotek , thanks for the feedback. updated the minor version.

@martykuentzel
Copy link

bump

Copy link

@jorik90 jorik90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two things worth noting:

  1. You've made changes in file that are generated. These changes will be overwritten.
  2. I've proposed an alternative solution to probably solve your problem. See my comment in kube-state alert routing in multi tenant cluster #1231 (comment)

@@ -29,7 +29,10 @@ spec:
description: '{{`{{`}} printf "%.4g" $value {{`}}`}}% of the {{`{{`}} $labels.job {{`}}`}}/{{`{{`}} $labels.service {{`}}`}} targets in {{`{{`}} $labels.namespace {{`}}`}} namespace are down.'
runbook_url: {{ .Values.defaultRules.runbookUrl }}alert-name-targetdown
summary: One or more targets are unreachable.
expr: 100 * (count(up == 0) BY (job, namespace, service) / count(up) BY (job, namespace, service)) > 10
expr: |-
{{ .Values.defaultRules.expressionPrefix }}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a change in a generated file (see the comment at the top of the file). When the next rules-sync is executed, your changes will be reverted.

@nrobert13
Copy link
Author

thanks for the proposed solution. closing this.

@nrobert13 nrobert13 closed this Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

kube-state alert routing in multi tenant cluster
4 participants