-
Notifications
You must be signed in to change notification settings - Fork 45
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
Store the Alertmanager notification configurations as a service configuration #2262
Labels
topic:operations
Operations-related issues
Comments
Ebaneck
added
topic:operations
Operations-related issues
topic: cluster&service configuration
Anything related to cluster and service configuration persistence
labels
Feb 26, 2020
Ebaneck
removed
the
topic: cluster&service configuration
Anything related to cluster and service configuration persistence
label
Feb 27, 2020
Ebaneck
added a commit
that referenced
this issue
Mar 5, 2020
… template engine Using the helm template engine with Alertmanager configurations (Alertmanager.yaml) does not seem to work as expected. It looks like the helm template engine does not recognise any new config values since all configuration use cases are not templated. We resolve to creating a new secret which will be used to override the default values making it possible for users to edit the configuration settings. Closes: #2262
Ebaneck
added a commit
that referenced
this issue
Mar 5, 2020
… template engine Using the helm template engine with Alertmanager configurations (Alertmanager.yaml) does not seem to work as expected. It looks like the helm template engine does not recognise any new config values since all configuration use cases are not templated. We resolve to creating a new secret which will be used to override the default values making it possible for users to edit the configuration settings. Closes: #2262
Ebaneck
added a commit
that referenced
this issue
Mar 5, 2020
… template engine Using the helm template engine with Alertmanager configurations (Alertmanager.yaml) does not seem to work as expected. It looks like the helm template engine does not recognise any new config values since all configuration use cases are not templated. We resolve to creating a new secret which will be used to override the default values making it possible for users to edit the configuration settings. Closes: #2262
Ebaneck
added a commit
that referenced
this issue
Mar 5, 2020
…emplate engine Using the helm template engine with Alertmanager configurations (Alertmanager.yaml) does not seem to work as expected. It looks like the helm template engine does not recognise any new config values since all configuration use cases are not templated. We resolve to creating a new secret which will be used to override the default values making it possible for users to edit the configuration settings. Closes: #2262
Ebaneck
added a commit
that referenced
this issue
Mar 6, 2020
…emplate engine Using the helm template engine with Alertmanager configurations (Alertmanager.yaml) does not seem to work as expected because the templated variables are directly base64 encoded instead of being replaced during the yaml dump. We resolve to creating a new secret which will be used to override the default values making it possible for users to edit the configuration settings. Closes: #2262
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component:
'salt', 'kubernetes', 'alertmanager'
Why this is needed:
For persistence of Alertmanager notification configurations, we need to store these service configurations using a ConfigMap.
Here, we are talking about integrations to Slack, email(smtp), victorops etc
What should be done:
Implementation proposal (strongly recommended):
Test plan:
Epic #1996
The text was updated successfully, but these errors were encountered: