From 3f1279c3dbff2ecb503c4844f988f595c65c4a0b Mon Sep 17 00:00:00 2001 From: chenhuan Date: Sat, 11 Aug 2018 20:08:54 +0800 Subject: [PATCH] fix the command output (#9815) I have verified on version v1.11 --- .../connecting-frontend-backend.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md b/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md index 6269dd520c..2329fbaad5 100644 --- a/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md +++ b/content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md @@ -144,8 +144,8 @@ kubectl create -f https://k8s.io/examples/service/access/frontend.yaml The output verifies that both resources were created: ``` -deployment "frontend" created -service "frontend" created +deployment.apps/frontend created +service/frontend created ``` **Note**: The nginx configuration is baked into the @@ -167,16 +167,16 @@ This displays the configuration for the `frontend` Service and watches for changes. Initially, the external IP is listed as ``: ``` -NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE -frontend 10.51.252.116 80/TCP 10s +NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE +frontend ClusterIP 10.51.252.116 80/TCP 10s ``` As soon as an external IP is provisioned, however, the configuration updates to include the new IP under the `EXTERNAL-IP` heading: ``` -NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE -frontend 10.51.252.116 XXX.XXX.XXX.XXX 80/TCP 1m +NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE +frontend ClusterIP 10.51.252.116 XXX.XXX.XXX.XXX 80/TCP 1m ``` That IP can now be used to interact with the `frontend` service from outside the