Tyler Helmuth

@haseeb-aziz Please format your post as yaml

@jsirianni this topic has come up before, here is the related issue for context: https://github.com/open-telemetry/opentelemetry-helm-charts/issues/242

Do you have a use case in mind that requires more configurability to the readiness and liveness sections?

Being able to configure [these options](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes) sounds like a good idea.

Being able to configure ports is also acceptable.

@DavidS-om it looks like you solved your issue by setting `.Values.config.receivers.jaeger` to `null` and then not including it in the traces pipeline, but it is not clear to me why...

Our CI does not test this chart in a IPv6 environment so I'm getting that's is the issue.

I don't think we can do that without breaking `IPv4` support by default.

@kentquirk the values.yaml is building the endpoint string itself with the assumption that the value from k8s downward api sets `MY_POD_IP` with a usable ip address.

The OpenTelemetryCollector object does let you specify a image pull policy. Using https://opentelemetry.io/docs/k8s-operator/automatic/#create-an-opentelemetry-collector-optional as the starting point, I believe you can do ``` kubectl apply -f -