UDP protocol is causing ingress errors about helm-charts

[niclic]

However, since I am revising this chart in preparation for migration to the prometheus-community chart repo, I will review the ingress implementation from scratch. I don't think the config in values.yaml is clear enough, and it might be a good idea to upgrade the ingress resource version as well.

[niclic]

My recollection is using ingress to expose the /metrics endpoint, so the metrics could be viewed in a browser, which is useful for troubleshooting. This requires exposing the webPort of the service, and not the udpPort or tcpPort ports. So, I don't think I experienced the same issue you did.

[yaron-idan]

That's great to hear, good luck with that!
I've already deployed my own version of the chart with a few modifications, it addresses the way these different protocols are handled. You're welcome to take a look and if you are interested I can open a PR so you can merge them back into your repository.

[niclic]

Yes, after review, the ingress resource was not properly implemented in this chart. For migration, I considered removing it altogether. However, I have modified it to expose the /metrics endpoint for viewing (or even scraping), which can be useful.

To make this chart expose the tcp and udp endpoints for metrics collection outside a cluster, will require additional work. That can certainly happen, since it does seem to be to be a valid use case. However, the chart will need to support exposing multiple ports, which may require patching of the ingress controller. It's complicated, so probably requires a bit of consideration (e.g. multiple services, etc).

I really appreciate your interest in this and sorry again for the lack of timely feedback. I had an issue with my github notifications.