You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user CP module for managing Slack Alertmanager Route configs
As part of removing our dependency on git-crypt for secrets currently managed in infrastructure repo, we should look at viability of offloading alert manager configs to users themselves. This might look something like:
user creates kubernetes secret containing webhook, channel, severity
module is called, passing k8s secret as input
trigger the templating of new config into the existing config data (would need to look at decoupling existing yaml from the Prometheus chart values)
Benefits:
users manage alertmanager routes themselves (less work for us)
clean up components infrastructure (much less terraform read / verbose pipeline output / faster plan and applies
one less thing managed via git-crypt
The text was updated successfully, but these errors were encountered:
Background
Proposal:
A user CP module for managing Slack Alertmanager Route configs
As part of removing our dependency on git-crypt for secrets currently managed in infrastructure repo, we should look at viability of offloading alert manager configs to users themselves. This might look something like:
Benefits:
components
infrastructure (much less terraform read / verbose pipeline output / faster plan and appliesThe text was updated successfully, but these errors were encountered: