whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct "kubectl get services" output.

Browse Source 
$ 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
This commit is contained in:
Marcin Owsiany
2016-04-01 14:49:28 +02:00
parent d956b20b4d
commit 46e667acd5
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/hellonode.md
+4 -4
View File
@@ -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.