Cherry-pick #24913 to 7.x: Add kubernetes_leaderelection provider #24984
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #24913 to 7.x branch. Original message:
What does this PR do?
Adds support for leaderelection provider in Agent based on #24267.
After this one is merged I plan to tune standalone manifest in follow-up PR so as to remove deployment section and only deploy as Deamonset with leaderelection "on".
Why is it important?
To support cluster wide metrics collection by only one Agent at a time between a group of multiple Agents (ie Deamonset).
On a second step we can change the standalone manifest, completely remove the Deployment of Agent and go on with only the Daemonset leveraging the leaderelection feature.
How to test this PR locally
./elastic-agent -e -d "*" -c /elastic-agent.yml inspect output -o default
Related issues