-
Notifications
You must be signed in to change notification settings - Fork 103
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
Liqoctl Force Unpeer Command #1112
Closed
Closed
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
Hi @aleoli. Thanks for your PR! I am @adamjensenbot.
Make sure this PR appears in the liqo changelog, adding one of the following labels:
|
aleoli
force-pushed
the
aol/force-unpeer
branch
2 times, most recently
from
February 15, 2022 14:08
5ade7cd
to
9cf0180
Compare
aleoli
force-pushed
the
aol/force-unpeer
branch
5 times, most recently
from
March 11, 2022 11:07
2a63e8f
to
20d4864
Compare
aleoli
force-pushed
the
aol/force-unpeer
branch
4 times, most recently
from
March 14, 2022 16:09
ec4218e
to
c665d76
Compare
/test |
giorio94
reviewed
Mar 23, 2022
aleoli
force-pushed
the
aol/force-unpeer
branch
5 times, most recently
from
April 4, 2022 14:33
06d06c4
to
1845d60
Compare
/test |
/test |
aleoli
added a commit
to aleoli/liqo
that referenced
this pull request
Apr 6, 2022
aleoli
added a commit
to aleoli/liqo
that referenced
this pull request
Apr 6, 2022
/test |
giorio94
approved these changes
Apr 15, 2022
aleoli
force-pushed
the
aol/force-unpeer
branch
2 times, most recently
from
April 19, 2022 09:57
47d3474
to
60abbd8
Compare
/hold Waiting for the linter to be fixed. |
/rebase test=true |
adamjensenbot
force-pushed
the
aol/force-unpeer
branch
from
May 10, 2022 10:33
60abbd8
to
26e4656
Compare
/rebase test=true |
aleoli
force-pushed
the
aol/force-unpeer
branch
from
August 2, 2022 09:28
26e4656
to
0593871
Compare
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
This pr adds a command to (force) purge a liqo peering between 2 clusters
In particular, it adds 2 ways:
liqoctl purge --kubeconfig-1 liqo_kubeconf_1 --kubeconfig-2 liqo_kubeconf_2
providing both the kubeconfigs. It cleans the peering from both clustersliqoctl purge --kubeconfig-1 liqo_kubeconf_1 --remote-cluster other-cluster
providing the kubeconfig of one of the two and the name of the other. It cleans the peering from a cluster (useful when the other cluster is no more reachable)How Has This Been Tested?