add k8s_leader_elector otel extension

[rogercoll]

What does this PR do?

Adds the K8s leader elector Otel Extension: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/k8sleaderelector

Why is it important?

Kube-stack Helm Chart is going to rely on this extension for cluster-wide events and metrics: open-telemetry/opentelemetry-helm-charts#1735

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @rogercoll? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[pkoutsovasilis]

@rogercoll , thinking out loud, are you sure we should add new components to already released versions (backport labels)? 🙂

cc @cmacknz @ebeahan @AlexanderWert

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[rogercoll]

@rogercoll , thinking out loud, are you sure we should add new components to already released versions (backport labels)? 🙂

Not a strong opinion, the idea for backporting to active-9 and active-8 was to be able to unify the kube-stack configuration once open-telemetry/opentelemetry-helm-charts#1735 is available across all supported branches. (Similar to #8917)

Would you suggest targeting new major and minor versions only?

[pkoutsovasilis]

What you say makes sense to me but I am not sure it is aligned with the "accepted changes for already released versions" policy we might have. I trust though that one of, if not all, of @ebeahan @pierrehilbert @AlexanderWert @cmacknz do know 🙂

[pierrehilbert]

EDIT: after re-reading and discussed with @pkoutsovasilis please forget my previous comment.
I'm not against backporting that one as we did it for the other PR

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: b284a48

cc @rogercoll

[swiatekm]

@rogercoll the extension you're adding here depends on the otel core framework 0.129.0, but we have earlier versions in other branches and don't plan to upgrade them. Will that work?

[rogercoll]

@rogercoll the extension you're adding here depends on the otel core framework 0.129.0, but we have earlier versions in other branches and don't plan to upgrade them. Will that work?

Good point, and no, it does not compile the agent correctly due to some APIs dependencies misalignment. Changed the target backports to the branches updated to 0.129.0 collector dependencies.