Alertmanager auto override label with matchers is current kubernetes namespace

duongneo commented 1 year ago

Describe the bug a clear and concise description of what the bug is.

Every time I add a new contact point for AlertManager, I always receive an overridder matchers with the namespace of the Kubernetes that I have Helm installed as the value and the namespace of the label.

What's your helm version?

v3.10.3

What's your kubectl version?

1.26

Which chart?

prometheus-community/kube-prometheus-stack

What's the chart version?

45.10.1

What happened?

Every time I add a new contact point for AlertManager, I always receive an overridder matchers with the namespace of the Kubernetes that I have Helm installed as the value and the namespace of the label.

Command: 'helm install monitoring prometheus-community/kube-prometheus-stack --namespace monitoring -f kube-prometheus-stack-values.yaml' Content of kube-prometheus-stack-values.yaml: grafana: enabled: false # Not install Grafana prometheus: enabled: false # Not install Prometheus alertmanager: enabled: true service: type: LoadBalancer # Create a public IP for Alertmanager alertmanagerSpec: alertmanagerConfigSelector: matchLabels: alertmanagerconfig: delivery-infras
config: global: resolve_timeout: 5m route: group_wait: 10s group_interval: 5m repeat_interval: 30m receiver: 'default' # receiver name for default (root) route configuration routes: receivers:

name: 'default' # default receiver name templates:
'/etc/alertmanager/config/*.tmpl'

Content of contact point: apiVersion: monitoring.coreos.com/v1alpha1 kind: AlertmanagerConfig metadata: name: rules namespace: prometheus labels: alertmanagerconfig: XXXXXX spec: route: receiver: 'grafana-default-alert' receivers:

name: 'grafana-default-alert' snsConfigs:
- topicARN: 'arn:aws:sns:XXXX:XXXX:XXXXX' sigv4: region: XXXX accessKey: key: accessKey name: sns-config secretKey: key: secretKey name: sns-config

What you expected to happen?

I do not want the matchers value in my contact point configuration file to be changed.

How to reproduce it?

No response

Enter the changed values of values.yaml?

No response

Enter the command that you execute and failing/misfunctioning.

helm install monitoring prometheus-community/kube-prometheus-stack --namespace monitoring -f kube-prometheus-stack-values.yaml

Anything else we need to know?

No response

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

stale[bot] commented 1 year ago

This issue is being automatically closed due to inactivity.

hugree commented 2 months ago

@duongneo did you ever solve it? I have the same issue

prometheus-community / helm-charts