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
Ansible: add leader election flags, use lease-based election #3457
Merged
jmrodri
merged 2 commits into
operator-framework:master
from
jmrodri:ansible-leader-election
Jul 22, 2020
Merged
Ansible: add leader election flags, use lease-based election #3457
jmrodri
merged 2 commits into
operator-framework:master
from
jmrodri:ansible-leader-election
Jul 22, 2020
Conversation
This file contains 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
jmrodri
changed the title
Ansible: add leader election flags, use lease-based election
[WIP] Ansible: add leader election flags, use lease-based election
Jul 18, 2020
openshift-ci-robot
added
the
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
label
Jul 18, 2020
92 tasks
camilamacedo86
approved these changes
Jul 18, 2020
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.
Juts missing a nit to pass in the CI
However, it shows great
/lgtm
joelanford
approved these changes
Jul 20, 2020
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
jmrodri
force-pushed
the
ansible-leader-election
branch
from
July 20, 2020 21:40
d859ddc
to
1ea183f
Compare
New changes are detected. LGTM label has been removed. |
jmrodri
changed the title
[WIP] Ansible: add leader election flags, use lease-based election
Ansible: add leader election flags, use lease-based election
Jul 20, 2020
openshift-ci-robot
removed
the
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
label
Jul 20, 2020
jmrodri
force-pushed
the
ansible-leader-election
branch
3 times, most recently
from
July 21, 2020 01:47
8697445
to
4fdaee9
Compare
joelanford
approved these changes
Jul 21, 2020
fabianvf
reviewed
Jul 21, 2020
jmrodri
force-pushed
the
ansible-leader-election
branch
from
July 22, 2020 15:34
4fdaee9
to
918ac16
Compare
openshift-ci-robot
added
the
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
label
Jul 22, 2020
jmrodri
force-pushed
the
ansible-leader-election
branch
from
July 22, 2020 15:39
918ac16
to
ebfd62c
Compare
openshift-ci-robot
removed
the
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
label
Jul 22, 2020
16 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of the change:
Ansible operator: add leader election flags, use controller-runtime leader election
Motivation for the change:
In general, the controller-runtime leader election method (lease-based) is preferable for most use cases. In the future, if there is a use case to support leader-for-life, we can add another flag to let operator developers choose their leader election mechanism.
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments
(seechangelog/fragments/00-template.yaml
)website/content/en/docs