Issue with k8s.io/docs/tasks/access-application-cluster/connecting-frontend-backend/

[jitendrabhalothia]

This is a...

• Feature Request
• Bug Report

Problem:
kubectl get service frontend
The external IP field may take some time to populate. If this is the case, the external IP is 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:

Proposed Solution:
Let's not to say repeat the same command until it shows an external IP address, let's use the --watch switch
Now :
kubectl get service frontend --watch

Better to add "--watch " switch, for instance, "kubectl get service frontend --watch" instead of telling to keep executing the same command for recent updates in the pod state.

Page to Update:
https://kubernetes.io/docs/tasks/access-application-cluster/connecting-frontend-backend/

[steveperry-53]

I will ask @juneharton to work on this.

[steveperry-53]

/assign @juneharton

[jitendrabhalothia]

Thanks, @steveperry-53.

@juneharton let me know if you need any clarification.

[jitendrabhalothia]

Any updates @steveperry-53 @juneharton.

[jitendrabhalothia]

@lucperkins are we adding watch switch to the requested doc?

[lucperkins]

@jitendrabhalothia Yes. See pull request #9129 for the proposed changes.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten