Makes the "all-in-one" Jaeger Kube service resource for jaeger-collector optionally "headless".
Some products (Kong) cannot connect properly to the Jaeger pods when the jaeger-collector service endpoint does not have an assigned cluster IP.
Which issue this PR fixes
Issue seen in OTLP compatible telemetry services, in this case Kong, where they cannot connect properly to a headless endpoint in Kubernetes, when it is serving the jaeger-collector OTLP-over-HTTP, on port 4318.
[x] Title of the PR starts with chart name ([jaeger] or [jaeger-operator])
[x] README.md has been updated to match version/contain new values (N/A - allInOne values are not documented in depth in the readme. Should I add an explanation of what this does?)
What this PR does
Makes the "all-in-one" Jaeger Kube service resource for jaeger-collector optionally "headless".
Some products (Kong) cannot connect properly to the Jaeger pods when the jaeger-collector service endpoint does not have an assigned cluster IP.
Which issue this PR fixes
Issue seen in OTLP compatible telemetry services, in this case Kong, where they cannot connect properly to a headless endpoint in Kubernetes, when it is serving the jaeger-collector OTLP-over-HTTP, on port 4318.
Checklist
[jaeger]or[jaeger-operator])