Use AlertmanagerConfig
resource instead of CSC ConfigMap
#3539
Labels
complexity:medium
Something that requires one or few days to fix
kind:enhancement
New feature or request
topic: cluster&service configuration
Anything related to cluster and service configuration persistence
topic:monitoring
Everything related to monitoring of services in a running cluster
Component: alertmanager, csc
Why this is needed: CSC is harder to use, since it isn't reactive and requires a Salt orchestration.
What should be done:
alertmanager.useExistingSecret
and.secrets
keys from the kube-prometheus-stack chart configuration, and define an appropriate.alertmanagerSpec.alertmanagerConfigSelector
and.alertmanagerConfigNamespaceSelector
AlertmanagerConfig
object (with the same values as today insalt/metalk8s/addons/prometheus-operator/config/alertmanager.yaml
)Test plan:
See prometheus-operator/prometheus-operator#3451
The text was updated successfully, but these errors were encountered: