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

Sample implementation of using Kubernetes leases instead of daemonset lock #835

Closed
wants to merge 1 commit into from

Conversation

jmcshane
Copy link

Resolves #25

This is a demo implementation that I have working in my local environment. We can't directly use the leaderelection package from client-go without some modification (the daemonset will persist post restart of the node, so the original context of leader election will be lost).

Would love to chat about this implementation and get it ready for inclusion in this library. Thanks for your work on this great tool!

Copy link

This PR was automatically considered stale due to lack of activity. Please refresh it and/or join our slack channels to highlight it, before it automatically closes (in 7 days).

@evrardjp
Copy link
Collaborator

evrardjp commented Oct 1, 2024

I would like to dig deeper into this. I need to understand more about leases behaviour, api impact on large clusters. Okay to discuss this ? I added you on linkedin for better coordination.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

lock on a separate/safe object rather than DaemonSet
2 participants