parent
3d70c1622f
commit
3f1279c3db
|
@ -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 `<pending>`:
|
||||
|
||||
```
|
||||
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
frontend 10.51.252.116 <pending> 80/TCP 10s
|
||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
frontend ClusterIP 10.51.252.116 <pending> 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
|
||||
|
|
Loading…
Reference in New Issue