Charts: [stable/grafana] Notification Channels / Notifiers as Secrets

[c089]

I've been setting up immutable deployments of grafana using the helm chart with and like it a lot so far! A thing that I missed today was the ability to provide notification channel configuration via kubernetes secret resources, as they often contain credentials such as passwords or API tokens for notification services.

[c089]

And just now I realized it could probably just be done by binding a secret to environment variable and using environment substitution in the provisioning file....

[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.

[wcarlsen]

We are facing the same issue as @c089 and being able to mount notifiers as a secret would increase security a lot.

[HenrikStanley]

My team is also facing a security issue with the token for our slack channel being exposed in the configmap.

Being able to define the notifier as a secret would help mitigate this.

[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.