Possibility to set another set of custom ports

[mateusz-bajorek]

In my org we wanted to deploy two splunk-otel-collectors alongside each other with different jobs to handle (collecting original kv-formatted and new json-formatted logs and passing them on to different splunk_platform_hec_tokens).

Request:
We would like to request making the two ports (13133 and 8889) as configurable parameters.

Reason:
We managed to change 3x ports that the application needs so that the default ports could be scheduled to the k8s worker nodes.

However, the pods are now crashing because they want to use a hardcoded healthcheck port, that cannot be changed without forking the application’s Helm chart: https://github.com/signalfx/splunk-otel-collector-chart/blob/main/helm-charts/splunk-otel-collector/templates/daemonset.yaml#L328 (since this application uses resources of the host nodes, the healthcheck ports are also bound on the host nodes, therefore this is not isolated like in the case of regular applications, where e.g. all Java applications can just use a pod port 9500; in this case, otel collector needs the pod port to also be available on the host instance).

It also needs a 5th port, TCP,8889, which is also hardcoded.

So overall, only one instance of Otel collector can run on a single Kubernetes cluster in our setup where we deploy the application using this helm chart. We cannot take down the old collector, as we still need the original (kv) formatted logs from it.