Skip to content
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

Operator leader election: use Leases only #6717

Merged
merged 1 commit into from
Apr 25, 2023

Conversation

barkbay
Copy link
Contributor

@barkbay barkbay commented Apr 21, 2023

Fix #4150

Note that this PR does not remove the ConfigMap, I wasn't sure if it's really worth making an API call every time the operator starts? (no strong opinion though...)

@barkbay barkbay added >enhancement Enhancement of existing functionality >refactoring v2.8.0 labels Apr 21, 2023
Copy link
Contributor

@thbkrkr thbkrkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't sure if it's really worth making an API call every time the operator starts? (no strong opinion though...)

Same. Hard to decide. It's not super clean but it doesn't bother. It would imply an API call every time the operator starts, but there is a cache. I'm a little more on the side of it is not worth it.

@barkbay barkbay merged commit c137ba0 into elastic:main Apr 25, 2023
@barkbay barkbay deleted the move-to-leases branch April 25, 2023 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement Enhancement of existing functionality >refactoring v2.8.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Switch leader election to use Leases
2 participants