From 46e667acd590eee1ae26d174fee5e07fc3732c98 Mon Sep 17 00:00:00 2001 From: Marcin Owsiany Date: Fri, 1 Apr 2016 14:49:28 +0200 Subject: [PATCH] Correct "kubectl get services" output. $ gcloud components list Your current Cloud SDK version is: 103.0.0 [...] $ kubectl get services NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE hello-node3 10.3.248.68 192.158.31.19 8080/TCP 14m --- docs/hellonode.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/hellonode.md b/docs/hellonode.md index 6d04c9fcf6..402a76a3fd 100755 --- a/docs/hellonode.md +++ b/docs/hellonode.md @@ -214,16 +214,16 @@ To find the ip addresses associated with the service run: ```shell $ kubectl get services hello-node -NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE -hello-node 10.3.246.12 8080/TCP run=hello-node 23s +NAME CLUSTER_IP EXTERNAL_IP PORT(S) AGE +hello-node 10.3.246.12 8080/TCP 23s ``` The `EXTERNAL_IP` may take several minutes to become available and visible. If the `EXTERNAL_IP` is missing, wait a few minutes and try again. ```shell $ kubectl get services hello-node -NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE -hello-node 10.3.246.12 23.251.159.72 8080/TCP run=hello-node 2m +NAME CLUSTER_IP EXTERNAL_IP PORT(S) AGE +hello-node 10.3.246.12 23.251.159.72 8080/TCP 2m ``` Note there are 2 IP addresses listed, both serving port 8080. `CLUSTER_IP` is only visible inside your cloud virtual network. `EXTERNAL_IP` is externally accessible. In this example, the external IP address is 23.251.159.72.