-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Enable Multi Cluster alerts by default #2099
Conversation
@philipgough do you have some time for a review here? |
@jkroepke - kicked off the pipeline and it fails, can you rebase? |
@philipgough rebased. |
@simonpasquier - would you mind taking a look here? I think this makes sense to me but I wan't to see how it looks from your side? |
I would appreciate a review before a next merge conflict appears :) |
No objection from my side. Ideally it should be consistent and there should be a single config parameter in kube-prometheus while right now, it seems that some mixins support toggling multi-cluster on/off while for others, it's hard-coded. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Thanks Simon, followed up with #2120 based on your comment |
Description
Fixes #2056
Type of change
What type of changes does your code introduce to the kube-prometheus? Put an
x
in the box that apply.CHANGE
(fix or feature that would cause existing functionality to not work as expected)FEATURE
(non-breaking change which adds functionality)BUGFIX
(non-breaking change which fixes an issue)ENHANCEMENT
(non-breaking change which improves existing functionality)NONE
(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Changelog entry
Please put a one-line changelog entry below. Later this will be copied to the changelog file.