Charts: [stable/prometheus-operator] Alertmanager config not loaded / crashloopback

[phouri]

Kubernetes version: v1.11.8 (GKE)
Helm/Tiller version: v2.13.1

Which chart:
stable/prometheus-operator

What happened:
Alertmanager is crashing, can't find the configurations we loaded into the values.

Configuration:

global:
      smarthost: ****
      auth_username: ****
      auth_identity: ****
      auth_password: ***
      resolve_timeout: 5m
      slack_api_url: 'https://hooks.slack.com/***'
      send_resolved: true

The alertmanager keeps crashing with the following error:
msg="Loading configuration file failed" file=/etc/alertmanager/config/alertmanager.yaml err="yaml: unmarshal errors:\n line 2: field auth_identity not found in type config.plain\n line 3: field auth_password not found in type config.plain\n line 4: field auth_username not found in type config.plain\n line 6: field send_resolved not found in type config.plain\n line 8: field smarthost not found in type config.plain"

What you expected to happen:
Alertmanager to load

How to reproduce it (as minimally and precisely as possible):
Basically did nothing but installing the helm chart, but since I couldn't find any documentation and/or other errors I guess something must have gone wrong.

Anything else we need to know:
I checked the secret - it got created successfully with the correct data as base64.

Appreciate any help on the matter.

[popsonebz]

facing same issue

[stale[bot]]

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.

[phouri]

Not stale 😑

[stale[bot]]

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.

[phouri]

Not stale... although the repo might be

[stale[bot]]

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.

[phouri]

Nope.

On Fri, 26 Jul 2019 at 10:41 stale[bot] [e-mail] wrote:

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.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/helm/charts/issues/13109?email_source=notifications&email_token=ABHPBIT2DQWR75FZJ6SCROLQBKTA3A5CNFSM4HGSW4G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD23YZFA#issuecomment-515345556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHPBIXMDHJTK6URV4K4TOLQBKTA3ANCNFSM4HGSW4GQ
.

[stale[bot]]

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]]

This issue is being automatically closed due to inactivity.

[pramodsharma62]

Has this been resolved? I am facing the same issue.