From 2a6085670bf8856bb6a3133bf608ed3d5f59a857 Mon Sep 17 00:00:00 2001 From: Sherlock113 Date: Mon, 21 Sep 2020 10:00:44 +0800 Subject: [PATCH] Update porter link Signed-off-by: Sherlock113 --- .../enable-multicluster/agent-connection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/multicluster-management/enable-multicluster/agent-connection.md b/content/en/docs/multicluster-management/enable-multicluster/agent-connection.md index cde6ef95c..d5c6f9599 100644 --- a/content/en/docs/multicluster-management/enable-multicluster/agent-connection.md +++ b/content/en/docs/multicluster-management/enable-multicluster/agent-connection.md @@ -85,7 +85,7 @@ NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) tower LoadBalancer 10.233.63.191 139.198.110.23 8080:30721/TCP 16h ``` -Note: Generally, there is always a LoadBalancer solution in the public cloud, and the external IP can be allocated by the load balancer automatically. If your clusters are running in an on-premises environment, especially a **bare metal environment**, you can use [Porter](https://github.com/porter/porter) as the LB solution. +Note: Generally, there is always a LoadBalancer solution in the public cloud, and the external IP can be allocated by the load balancer automatically. If your clusters are running in an on-premises environment, especially a **bare metal environment**, you can use [Porter](https://github.com/kubesphere/porter) as the LB solution. {{}}