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.

Sign up for GitHub

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

Jump to bottom

Support leader takeover #23

Closed
buehler opened this issue May 20, 2020 · 1 comment
Closed

Support leader takeover #23

buehler opened this issue May 20, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@buehler
Copy link
Owner

buehler commented May 20, 2020

Regarding #22: It would be nice to "force" a leader to be set when using local development, so one can develop an operator on the same kubernetes instance that the deployed operator runs on.
@buehler buehler added the enhancement New feature or request label May 20, 2020
@buehler
Copy link
Owner Author

buehler commented Sep 9, 2020

This will not be possible without some strange magic.

Better way is to implement the namespaced only variant of the operator and then run the development version only in that namespace.

The normal leader election should take place via V1Lease object.

@buehler buehler closed this as completed Sep 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@buehler