Cherry-pick #25016 to 7.x: Leverege leader election in agent k8s manifests#25033
Merged
ChrsMark merged 1 commit intoelastic:7.xfrom Apr 13, 2021
Merged
Cherry-pick #25016 to 7.x: Leverege leader election in agent k8s manifests#25033ChrsMark merged 1 commit intoelastic:7.xfrom
ChrsMark merged 1 commit intoelastic:7.xfrom
Conversation
(cherry picked from commit b046d56)
Contributor
|
Pinging @elastic/integrations (Team:Integrations) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 #25016 to 7.x branch. Original message:
What does this PR do?
This PR tunes k8s manifests for elastic-agent so as to use leaderelection provider in order to enable cluster level monitoring only from one leader Pod at a time.
Why is it important?
Removing Deployment and using only Daemonset will simplify the deployment process for users.
Note: Tested on GKE 3-node cluster, leaderelection and all functionality works.