From 36ad19510a174625549489e0f9e387cd79064660 Mon Sep 17 00:00:00 2001 From: lucperkins Date: Mon, 18 Jun 2018 15:56:50 -0700 Subject: [PATCH 1/2] Use --watch flag instead of checking multiple times --- .../connecting-frontend-backend.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 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 c877a14e025f6..2cd66b0c695b4 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 @@ -160,24 +160,28 @@ Once you’ve created a Service of type LoadBalancer, you can use this command to find the external IP: ``` -kubectl get service frontend +kubectl get service frontend --watch ``` -The external IP field may take some time to populate. If this is the -case, the external IP is listed as ``. +This will display the configuration for the `frontend` Service and watch for +changes. Initially, the external IP will be listed as ``: ``` NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE frontend 10.51.252.116 80/TCP 10s ``` -Repeat the same command again until it shows an external IP address: +As soon as an external IP is provisioned, however, the configuration will be +updated 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 ``` +That IP can now be used to interact with the `frontend` service from outside the +cluster. + ### Send traffic through the frontend The frontend and backends are now connected. You can hit the endpoint @@ -189,7 +193,7 @@ curl http:// The output shows the message generated by the backend: -``` +```json {"message":"Hello"} ``` From 7eb1e913705c41befe1497dcb27fc7ab14db3d5f Mon Sep 17 00:00:00 2001 From: lucperkins Date: Wed, 27 Jun 2018 11:21:08 -0700 Subject: [PATCH 2/2] Wording changes --- .../connecting-frontend-backend.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 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 2cd66b0c695b4..b6e13a1e7dbe6 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 @@ -163,16 +163,16 @@ command to find the external IP: kubectl get service frontend --watch ``` -This will display the configuration for the `frontend` Service and watch for -changes. Initially, the external IP will be listed as ``: +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 ``` -As soon as an external IP is provisioned, however, the configuration will be -updated to include the new IP under the `EXTERNAL-IP` heading: +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