docs: add Helm Charts section

[clavinjune]

No description provided.

[mgumz]

@clavinjune the helm-chart or "a" helm chart would make more sense in the mtr-exporter repository and not in a "random" github-repo somewhere, referred to from README, pointing to an untagged "main" branch.

no sensible OPS person would / should ever install such a combination :)

both the Containerfile as well as Helm chart are kind of an "addon" and thus could both be placed into an "addon" or "support" folder in mtr-exporter repo. A grafana dashboard is another contender to be hosted in such a folder. since ghcr.io can host also helm-charts, one might argue that both the container as well as the chart should originate from the same source.

to your initial helm-template:

• https://github.com/clavinjune/helm-charts/blob/f5f382a48585a89f1eccbb1a9167b47d36359c64/charts/mtr-exporter/values.yaml#L99-L104 - autoscaling … so you intend to ddos destinations more easily? :)
• https://github.com/clavinjune/helm-charts/blob/f5f382a48585a89f1eccbb1a9167b47d36359c64/charts/mtr-exporter/templates/deployment.yaml#L43-L45 - you might want to add -watch-jobs here to pick up changes in the configmap
• https://github.com/clavinjune/helm-charts/blob/f5f382a48585a89f1eccbb1a9167b47d36359c64/charts/mtr-exporter/templates/deployment.yaml#L43-L45 - same spot: you might want to provide something like "additionalMtrArguments" or alike in order to support the various mtr-feature like "send udp packets", "-a " for when multus provide the mtr-exporter-pod a 2ndary, public ip from which the probes should be sent. yes, true, can be achieved via the jobs-file as well, so maybe a non-issue
• when there is a 2ndary interface and a public ip, the default "-bind :8080" does not cut it anymore (from a security pov). then you would need to "-bind POD_IP" … and this usually requires that you create an ENV variable similar like https://kubernetes.io/docs/tasks/inject-data-application/environment-variable-expose-pod-information/ and use that in a way around tini (so sh -c tini ... the rest ... -- -bind $POD_ID or alike)

so, in its current form i am hesitant to merge this PR.

[clavinjune]

for the moment, I'll close this PR and try to improved the charts in my environment. So as it is said, you'd like the helm-charts to be inside this repository as well?

[mgumz]

you'd like the helm-charts to be inside this repository as well?

Yah, I do not oppose a folder "support" or something like that which contains the Containerfile for people who operate mtr-exporter in a container runtime nor a Helm chart for people operating a zoo of mtr-exporters running on a zoo of container runtimes :)