Liqoctl Force Unpeer Command

[aleoli]

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 clusters
• liqoctl 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?

• [x] locally, with 2 running clusters
• [x] locally, with 1 running cluster
  • peer 2 kind clusters
  • delete 1 of the 2
  • purge the other one

[adamjensenbot]

Hi @aleoli. Thanks for your PR!

I am @adamjensenbot. You can interact with me issuing a slash command in the first line of a comment. Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests when the rebase operation is completed)
• /merge: Merge this PR into the master branch
• /build Build Liqo components
• /test Launch the E2E and Unit tests
• /doc-build Trigger the build of the Liqo documentation

Make sure this PR appears in the liqo changelog, adding one of the following labels:

• kind/breaking: :boom: Breaking Change
• kind/feature: :rocket: New Feature
• kind/bug: :bug: Bug Fix
• kind/cleanup: :broom: Code Refactoring
• kind/docs: :memo: Documentation

[aleoli]

/test

[aleoli]

/test

[aleoli]

/test

[aleoli]

/test

[giorio94]

/hold Waiting for the linter to be fixed.

[aleoli]

/rebase test=true

[aleoli]

/rebase test=true