diff options
| author | Fabio Busatto <fabio@gitlab.com> | 2018-02-07 13:50:02 +0000 |
|---|---|---|
| committer | Fabio Busatto <fabio@gitlab.com> | 2018-02-07 13:50:02 +0000 |
| commit | bf53d565c13e504e811234dadaf58495f57da30f (patch) | |
| tree | 65465d6149c523da0631ec4955efa41a94917e8a | |
| parent | c3926d47f49051c001f5a0f3068816a3cd68b972 (diff) | |
| download | gitlab-ce-docs/add-retrieving-external-ip.tar.gz | |
Add more information about external addressdocs/add-retrieving-external-ip
| -rw-r--r-- | doc/user/project/clusters/index.md | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/user/project/clusters/index.md b/doc/user/project/clusters/index.md index dd9902032cc..823df20f365 100644 --- a/doc/user/project/clusters/index.md +++ b/doc/user/project/clusters/index.md @@ -141,6 +141,9 @@ You need a load balancer installed in your cluster in order to obtain the external IP address with the following procedure. It can be deployed using the **Ingress** application described in the previous section. +In order to publish your web application, you first need to find the external IP +address associated to your load balancer. + If the cluster is on GKE, click on the **Google Kubernetes Engine** link in the **Advanced settings**, or go directly to the [Google Kubernetes Engine dashboard](https://console.cloud.google.com/kubernetes/) @@ -162,7 +165,9 @@ Otherwise, you can list the IP addresses of all load balancers: kubectl get svc --all-namespaces -o jsonpath='{range.items[?(@.status.loadBalancer.ingress)]}{.status.loadBalancer.ingress[*].ip} ' ``` -The output is the external IP address of your cluster. +The output is the external IP address of your cluster. This information can then +be used to set up DNS entries and forwarding rules that allow external access to +your deployed applications. ## Setting the environment scope |