Skip to content

[Docs] Add declarative peering section #2813

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

Merged
adamjensenbot merged 1 commit into from
Nov 28, 2024
Merged

[Docs] Add declarative peering section #2813

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
1 change: 1 addition & 0 deletions docs/_toc.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,7 @@ subtrees:
- file: advanced/peering/inter-cluster-network.md
- file: advanced/peering/inter-cluster-authentication.md
- file: advanced/peering/offloading-in-depth.md
- file: advanced/peering/peering-via-cr.md
- file: advanced/use-only-offloading.md
- file: advanced/enable-external-networking.md
- file: advanced/virtualnode-customizations.md
Expand Down
12 changes: 6 additions & 6 deletions docs/advanced/peering/inter-cluster-authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,9 +208,9 @@ As a result of the command, you should be able to see:
NAME TYPE DATA AGE
liqo-signed-nonce Opaque 2 78s
```

```{admonition} Note
If you want to use the [in-band](UsagePeeringInBand) approach, use the `spec.proxyURL` field inside the `Tenant` CRD.
If you want to use the [in-band](UsagePeeringInBand) approach, use the `spec.proxyURL` field inside the `Tenant` CRD.
Check the [Kubernetes API Server Proxy](/advanced/k8s-api-server-proxy.md) page
```

Expand Down Expand Up @@ -259,11 +259,11 @@ spec:
status: {}
```

Which can be applied **on the cluster consumer**:
Which can be applied **on the cluster consumer**, making sure that the resource is created in the tenant namespace (`liqo-tenant-cl-consumer` in this case):

```{code-block} bash
:caption: "Cluster consumer"
kubectl apply -f $IDENTITY_RESOURCE_YAML_PATH
kubectl apply -f $IDENTITY_RESOURCE_YAML_PATH -n liqo-tenant-cl-consumer
```

Once the Identity resource is correctly applied, the clusters are able to negotiate the resources for the [offloading](/advanced/peering/offloading-in-depth).
Expand Down Expand Up @@ -292,10 +292,10 @@ All in all, these are the steps to be followed by the administrators of each of
liqoctl generate identity --remote-cluster-id $CLUSTER_CONSUMER_ID > identity.yaml
```

4. **Cluster consumer** applies `identity.yaml`:
4. **Cluster consumer** applies `identity.yaml` in the tenant namespace:

```bash
kubectl apply -f identity.yaml
kubectl apply -f identity.yaml -n $TENANT_NAMESPACE
```

You can check whether the procedure completed successfully by checking [the peering status](../../usage/peer.md#check-status-of-peerings).
Loading