Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommend --watch flag for obtaining external IP information (issue 8483) #9129

Merged
merged 3 commits into from
Jul 19, 2018
Merged

Recommend --watch flag for obtaining external IP information (issue 8483) #9129

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
36ad195
Use --watch flag instead of checking multiple times
lucperkins Jun 18, 2018
7eb1e91
Wording changes
lucperkins Jun 27, 2018
a010435
Merge remote-tracking branch 'upstream/master' into lperkins/issue-84…
lucperkins Jul 5, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions content/en/docs/tasks/access-application-cluster/connecting-frontend-backend.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 `<pending>`.
This will display the configuration for the `frontend` Service and watch for
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the style guide: use present tense.

This displays the configuration for the `frontend` Service and watches for

changes. Initially, the external IP will be listed as `<pending>`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more. 

external IP is listed


```
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
frontend 10.51.252.116 <pending> 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more. 

As soon as an external IP is provisioned, however, the configuration updates

updated to include the new IP under the `EXTERNAL-IP` heading:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more. 

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
Expand All @@ -189,7 +193,7 @@ curl http://<EXTERNAL-IP>

The output shows the message generated by the backend:

```
```json
{"message":"Hello"}
```

Expand Down