[liqoctl] generate peering-user #2911
Open
+1,104
−63
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 @claudiolor. Thanks for your PR! I am @adamjensenbot.
Make sure this PR appears in the liqo changelog, adding one of the following labels:
|
github-actions
bot
added
feat
claudiolor
force-pushed
the
clo/liqoctl-new-user
branch
from
f19a67a to
3ea3943
Compare
github-actions
bot
added
docs
claudiolor
force-pushed
the
clo/liqoctl-new-user
branch
8 times, most recently
from
0f0e212 to
f203cff
Compare
adamjensenbot
force-pushed
the
clo/liqoctl-new-user
branch
from
2be20b4 to
e162a78
Compare
claudiolor
force-pushed
the
clo/liqoctl-new-user
branch
2 times, most recently
from
6bb3540 to
063dd70
Compare
|
/test |
claudiolor
force-pushed
the
clo/liqoctl-new-user
branch
from
b3928aa to
064a423
Compare
This patch introduces a set of commands allowing to generate a user with the minimum permissions to create a peering from the cluster with the specified cluster ID
claudiolor
force-pushed
the
clo/liqoctl-new-user
branch
from
064a423 to
91f6e27
Compare
claudiolor
force-pushed
the
clo/liqoctl-new-user
branch
from
91f6e27 to
90029fe
Compare
frisso
reviewed
Feb 10, 2025
|
|
||
| To proceed, ensure that you are operating in the *consumer* cluster, and then issue the *liqoctl peer* command: | ||
| To create a peering with a *provider* cluster, you will require a kubeconfig with a set of permissions to establish a connection with it. |
There was a problem hiding this comment.
Suggested change
| To create a peering with a *provider* cluster, you will require a kubeconfig with a set of permissions to establish a connection with it. | |
| The setup of a peering with a *provider* cluster requires the creation of a `kubeconfig` tailored with the proper set of permissions to minimize security risks, namely, to allow only to the peering on the remote cluster while preventing any other actions on the other resources of the cluster. |
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 introduces a set of commands allowing to generate a user with the minimum permissions to create a peering from the cluster with the specified cluster ID.
To create an user with the minimum permissions to peer with the current cluster from a cluster with ID $CLUSTER_ID:
to remove all the permissions to the user: