[exporter/loadbalancingexporter] improve docs for k8s service resolver

[fyuan1316]

Component(s)

exporter/loadbalancing

Describe the issue you're reporting

This issue is a refinement of the FEAT #22776 document.

#22776 (review)

[github-actions]

Pinging code owners:

• exporter/loadbalancing: @jpkrohling

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• exporter/loadbalancing: @jpkrohling

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[jpkrohling]

I believe this has been done already. Closing.

[awangc]

@fyuan1316 Thank you for providing support for resolving k8s service. Apologies for asking questions on a closed issue, if there are other preferred venues for clarification questions, please let me know and I can follow up there.

The example provided uses the opentelemetry-operator for deployment. We're on a much older version of kubernetes and the operator won't work. Is it possible to just deploy the loadbalancerexporter as a service and connect it to a different backend service?

I think the main question I have is if the operator is enabling something that the exporter will need to be able to get updates when there are changes to the endpoints. TIA for the help!