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

controllers/factory/vmalert: do not add notifier.* flags if notifier.blackhole is set by user #895

Merged
merged 1 commit into from
Mar 7, 2024

Conversation

zekker6
Copy link
Contributor

@zekker6 zekker6 commented Mar 7, 2024

Previously, setting "notifier.blackhole" and not using any notifiers would lead to CrashLoopBackoff because vmalert would receive an empty "notifier.url" value.

Updates:

…blackhole is set by user

Previously, setting "notifier.blackhole" and not using any notifiers would lead to CrashLoopBackoff because vmalert would receive an empty "notifier.url" value.

Updates:
- #894
- #813
Copy link
Collaborator

@f41gh7 f41gh7 left a comment

Choose a reason for hiding this comment

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

LGTM

@f41gh7
Copy link
Collaborator

f41gh7 commented Mar 7, 2024

I think, it'd be great to set blackhole as a default value if there is no any notifiers configured.

@f41gh7 f41gh7 merged commit 9caa896 into master Mar 7, 2024
2 checks passed
@f41gh7 f41gh7 deleted the vmalert/notifier-blackhole branch March 7, 2024 22:42
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.

None yet

2 participants