You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ include "prometheus-redis-exporter.labels" . | indent 4 }}
annotations:
).
The related service monitor's namespace can be set with Values.serviceMonitor.namespace but not for the deployment.
This is a problem because my Helm chart is installed with a monitoring namespace, but I want the deployment for redis-exporter to be created in the same namespace as the Redis pods -- for sharing secrets.
Describe the solution you'd like.
The redis-exporter deployment should respect Values.namespace (a key that doesn't exist yet).
It would also make sense for this key to be the default for the related serviceMonitor unless Values.serviceMonitor.namespace is explicitly provided.
Describe alternatives you've considered.
NONE
Additional context.
I can contribute the needed change for this.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem ?
prometheus-redis-exporter
's deployment has no way to set the namespace (helm-charts/charts/prometheus-redis-exporter/templates/deployment.yaml
Lines 3 to 7 in 25238a6
The related service monitor's namespace can be set with
Values.serviceMonitor.namespace
but not for the deployment.This is a problem because my Helm chart is installed with a
monitoring
namespace, but I want the deployment forredis-exporter
to be created in the same namespace as the Redis pods -- for sharing secrets.Describe the solution you'd like.
The
redis-exporter
deployment should respectValues.namespace
(a key that doesn't exist yet).It would also make sense for this key to be the default for the related
serviceMonitor
unlessValues.serviceMonitor.namespace
is explicitly provided.Describe alternatives you've considered.
NONE
Additional context.
I can contribute the needed change for this.
The text was updated successfully, but these errors were encountered: