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

bug: Alertmanager deployment does not respect alertmanager.configMap value #1734

Closed
cwstrommer opened this issue Nov 11, 2024 · 2 comments · Fixed by #1735
Closed

bug: Alertmanager deployment does not respect alertmanager.configMap value #1734

cwstrommer opened this issue Nov 11, 2024 · 2 comments · Fixed by #1735

Comments

@cwstrommer
Copy link

Chart name and version
chart: victoria-metrics-alert
version: v0.12.4

Describe the bug
In our environment we manage the alertmanager routes and receiver configuration externally, and reference it via alertmanager.configMap when we render the Helm chart. Version 0.12.4 retains alertmanager.configMap in the values, but does not respect it because the Deployment spec changed from

        - name: config
          configMap:
            name: {{ include "vmalert.alertmanager.configname" . }}

to

        - name: config
          configMap:
            name: {{ $fullname }}-config

This causes the pod to fail with

  Warning  FailedMount      98s (x53 over 93m)  kubelet       MountVolume.SetUp failed for volume "config" : configmap "victoria-metrics-alert-alertmanager-config" not found

Custom values
Please provide only custom values (excluding default ones):

alertmanager:
  podMetadata:
    annotations:
      checksum/external-config: a40ca23bddd5c80ab3cf63c7dcb80844
  configMap: victoria-metrics-alert-external-config
@AndrewChubatiuk
Copy link
Collaborator

hey @cwstrommer
please try chart 0.12.5, which should contain fixes

@cwstrommer
Copy link
Author

hey @cwstrommer please try chart 0.12.5, which should contain fixes

Nice, thank you for the quick response! I'll test it over the next couple of days, you can assume that it's solved if you don't hear back from me.

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 a pull request may close this issue.

2 participants