Skip to content

Polishing docs for manual authentication #2863

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

Closed
frisso wants to merge 1 commit into from
Closed

Polishing docs for manual authentication #2863

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 10 additions & 8 deletions docs/advanced/manual-peering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
# Manual peering
# Custom peering

In the [peer two clusters](../usage/peer.md) section of this documentation, we used the `liqoctl peer`, which automatically configure each single module of Liqo to create a peering between two clusters. However, in some cases where:
In the [peer two clusters](../usage/peer.md) section of this documentation, we used the `liqoctl peer` command, which automatically configures all the Liqo modules (namely _networking_, _authentication_, and _offloading_) to create a peering between two clusters. However, there are some cases in which the automatic process is not appropriate, and the user would like to customize advanced parameters, overcome specific network constraints, and more, hence a more granular tuning for the peering process is needed.
For instance, we list here some cases in which the automatic peering is not a suitable choice:

- you want to configure Liqo peerings via a [declarative approach](./peering/peering-via-cr.md) via CRs.
- it is required to configure the WireGuard gateway server on the cluster consumer (e.g. the nodes of the cluster provider are [behind a NAT or a physical load balancer](./nat.md))
- The consumer needs to create multiple requests for resources (ResourceSlice) or you want to customize the way resources are distributed on virtual nodes
- you would like to configure Liqo the peerings via a [declarative approach](./peering/peering-via-cr.md), i.e., with Kubernetes CRs;
- you need to configure the WireGuard gateway server on the consumer cluster (e.g. the nodes of the provider cluster are [behind a NAT or a physical load balancer](./nat.md));
- the consumer needs to create multiple requests for resources (ResourceSlice) or you would like to customize how resources are distributed across virtual nodes.

you might need to configure each single module separatly, or to interact with a specific module to obtain the desired result.

In this section, you will discover how to interact with each Liqo module without using the automatic peering method.
To overcome the above necessities, Liqo allows to configure each module separately, with a more granual control.
This section shows how to interact with each individual Liqo module to better tune your peering process.

## Prerequirements

Expand All @@ -21,3 +21,5 @@ Check each module specific documentation to understand how to configure it:
- [Networking](/advanced/peering/inter-cluster-network)
- [Authentication](/advanced/peering/inter-cluster-authentication)
- [Offloading](/advanced/peering/offloading-in-depth)

Furthermore, an additional section describes how to interact with the above modules using [Kubernetes CRs](/advanced/peering/peering-via-cr), hence using a fully declarative approach.
Loading
Loading