-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Elasticsearch] Add condition and leader election to Elasticsearch integration #5353
Conversation
If I merge #4597 before this enhancement, this will only be available for 8.7+ since my PR requires newer versions of Agent. I lean towards merging mine first since it's been open for a while but I can give this one up to the EOW to be get reviewed and merged. I will trigger CI on this to get things moving. @miltonhultgren @klacabane it would be good to get your feedback on whether or not we want this enhancement. It seems reasonable to me but you all are the experts. |
/test |
🌐 Coverage report
|
- name: leaderelection | ||
type: bool | ||
title: Leader Election | ||
description: Enable leaderelection between a set of Elastic Agents running on Kubernetes. Useful for when scope is `cluster`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to link to this documentation ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think that doc only applies to Standalone deployments, I believe for fleet managed deployments, this automatically happens. (For the most part the wording was copy/pasted from other integrations that implement Leader Election, can be added though if desired)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/test |
Package elasticsearch - 1.3.0 containing this change is available at https://epr.elastic.co/search?package=elasticsearch |
1 similar comment
Package elasticsearch - 1.3.0 containing this change is available at https://epr.elastic.co/search?package=elasticsearch |
…tegration (elastic#5353) * Add condition and leader election to elasticsearch integration * Update changelog link * Update condition description wording
…tegration (elastic#5353) * Add condition and leader election to elasticsearch integration * Update changelog link * Update condition description wording
Enhancement
What does this PR do?
Checklist
changelog.yml
file.Author's Checklist
condition
is a top level of both inputs as I couldn't think of a reason where a user would want conditions to be different based on what is being collected within an input, and this greatly simplifies things for users.leaderelection
was added to the metrics input, because if you want to use thecluster
scope, you'd want only one Elastic Agent performing the collectioncondition
andleaderelection
are both under the advanced sections, as I'm not sure how many people would actually use this (I don't know how many users actually run Elasticsearch on Kubernetes)Integration Policy Before Upgrade
Integration Policy After Upgrade
Integration Policy After Upgrade & Adding Conditions/Leader Election
How to test this PR locally
Related issues
condition
#5319Screenshots