Description
Describe the bug a clear and concise description of what the bug is.
Unless you install with "--set config" you won't get "--config.file=/config/snmp.yaml" , mountpath, reloader ,etc. At one point I feel "--set config" would append to the created snmp.yaml, but now it only copies 1 for 1. When I try to include a config, its too large and the system chokes. If I just set the config to my auth, I get no modules or anything else. I tried to use kubectl edit cm but it ends up not allowing the "!" to include a file, but if I copy and paste it in it also tells me it's too large. So I'm stuck for a way to get a config map that has the default configuration that lets me edit it and then add what I need, save, and continue
What's your helm version?
version.BuildInfo{Version:"v3.14.3", GitCommit:"f03cc04caaa8f6d7c3e67cf918929150cf6f3f12", GitTreeState:"clean", GoVersion:"go1.21.7"}
What's your kubectl version?
Client Version: v1.28.8+k3s1 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.28.8+k3s1
Which chart?
promethus-snmp-exporter
What's the chart version?
latest
What happened?
Detailed above
What you expected to happen?
Detailed above
How to reproduce it?
Stuff all the config into a file:
helm upgrade --install prometheus-snmp-exporter --set config="$(cat theconfig)" prometheus-community/prometheus-snmp-exporter -n monitoring
Try to get the configmap created with the default info -
helm upgrade --install prometheus-snmp-exporter --set config=" " prometheus-community/prometheus-snmp-exporter -n monitoring
Do it with a copy paste:
kubectl edit cm prometheus-snmp-exporter -n monitoring
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
helm upgrade --install prometheus-snmp-exporter --set config="$(cat theconfig)" prometheus-community/prometheus-snmp-exporter -n monitoring
helm upgrade --install prometheus-snmp-exporter --set config=" " prometheus-community/prometheus-snmp-exporter -n monitoring
Anything else we need to know?
No response