This is some work on #34 . With this changes I can use the project in our/mine platform.
I changed how metadata namespace is handled. HELM saves some data in the cluster in the namespace provided by -n flag or --namespace.
Before this PR if you run helm install ms-exporter-testing helm the helm state will be install into default namespace and the objects into kube-system.
If you run helm install --namespace prometheus ms-exporter-testing helm the objects will be installed in kube-system and the state into prometheus. You have to read the implementation to deploy to a namespace you want to.
With the change the state and the objects are deployed in the same namespace you provide with the -n flag.
This is some work on #34 . With this changes I can use the project in our/mine platform.
I changed how metadata namespace is handled. HELM saves some data in the cluster in the namespace provided by
-nflag or--namespace. Before this PR if you runhelm install ms-exporter-testing helmthe helm state will be install intodefaultnamespace and the objects intokube-system. If you runhelm install --namespace prometheus ms-exporter-testing helmthe objects will be installed inkube-systemand the state intoprometheus. You have to read the implementation to deploy to a namespace you want to. With the change the state and the objects are deployed in the same namespace you provide with the-nflag.I have added annotations that can be used with the official prometheus helm chart. https://github.com/helm/charts/blob/master/stable/prometheus/values.yaml#L1470 With the annotations the Prometheus will pick up a pod/service without defining an explicit job.