You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/advanced/peering/inter-cluster-network.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,8 +77,8 @@ The Liqo Gateway of the first cluster will act as a client, while the one in the
77
77
```{admonition} Note
78
78
You can see further configuration options with `liqoctl network connect --help`.
79
79
80
-
For instance, in the previous command we have used the `--server-service-type NodePort` option to expose the service associated to the Liqo Gateway server as a NodePort.
81
-
Alternatively, you can use the `--server-service-type LoadBalancer` option to expose the Liqo Gateway service as a LoadBalancer (if supported in your Kubernetes cluster).
80
+
For instance, in the previous command we have used the `--gw-server-service-type NodePort` option to expose the service associated to the Liqo Gateway server as a NodePort.
81
+
Alternatively, you can use the `--gw-server-service-type LoadBalancer` option to expose the Liqo Gateway service as a LoadBalancer (if supported in your Kubernetes cluster).
82
82
```
83
83
84
84
In the first cluster (acting as gateway client), you can find the following resources:
0 commit comments