[receiver/k8sobject] support kubernetes leader election

[TylerHelmuth]

Component(s)

receiver/k8sobjects

Is your feature request related to a problem? Please describe.

Currently the receiver is only supported in Deployment mode, with 1 replica. The receiver should know how to take advantage of leader election so that it can be run with multiple replicas or as a daemonset. This allows

Describe the solution you'd like

The receiver should know how to take advantage of leader election so that it can be run with multiple replicas or as a daemonset. This allows the users to potentially slim their k8s deployment architecture to only a daemonset or deployment, instead of needing to put the receiver in a specific collector instance with only 1 replica.

Describe alternatives you've considered

No response

Additional context

• [receiver/k8seventsreceiver] support kubernetes leader election #17369
• [receiver/[k8sclusterreceiver] support kubernetes leader election #24678

[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.

[BharatKJain]

@TylerHelmuth The PR is marked as stale, is the PR unit-tests still pending? Checking if I can contribute to it or not by adding/fixing the unit-tests.

[ChrsMark]

Maybe we can merge this with #34460 which is more generic?