Open perry-mitchell opened 5 days ago
@perry-mitchell by default the chart doesn't not expose the port on the container. You can see a simple example here: https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-collector/examples/daemonset-only/rendered/daemonset.yaml.
If you need to add a port to the container you can use .Values.ports
: https://github.com/open-telemetry/opentelemetry-helm-charts/blob/6f674b102585a158dbacccecfc2c12a3bbc5a120/charts/opentelemetry-collector/values.yaml#L268
by default the chart doesn't not expose the port on the container.
Wouldn't it make sense to expose it, even by default, so it could be used as a healthcheck downstream?
.Values.ports
This doesn't work, and the helm chart throws an exception when I add a new port name that isn't listed there. I don't have the error on-hand anymore, unfortunately.
This configuration worked for me:
ports:
healthcheck:
enabled: true
containerPort: 13133
servicePort: 13133
protocol: TCP
I can't seem to get the healthcheck port exposed for some reason. I'm creating the release in terraform:
Current config:
(Though I've tried it with no options as well).
Yet it won't expose port
13133
:Looking at the
ports
configuration in the chart values, there doesn't even seem to be an entry for the healthcheck.Additionally, the created service for the collector, when enabled, does not expose such a port either.