Skip to content

Commit 992cfb1

Browse files
committed
changed output format
1 parent fde6659 commit 992cfb1

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

content/en/docs/concepts/services-networking/connect-applications-service.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,8 +46,9 @@ Check your pods' IPs:
4646

4747
```shell
4848
kubectl get pods -l run=my-nginx -o custom-columns=POD_IP:.status.podIPs
49-
podIP: 10.244.3.4
50-
podIP: 10.244.2.5
49+
POD_IP
50+
[map[ip:10.244.3.4]]
51+
[map[ip:10.244.2.5]]
5152
```
5253
5354
You should be able to ssh into any node in your cluster and use a tool such as `curl` to make queries against both IPs. Note that the containers are *not* using port 80 on the node, nor are there any special NAT rules to route traffic to the pod. This means you can run multiple nginx pods on the same node all using the same `containerPort`, and access them from any other pod or node in your cluster using the assigned IP address for the Service. If you want to arrange for a specific port on the host Node to be forwarded to backing Pods, you can - but the networking model should mean that you do not need to do so.

0 commit comments

Comments
 (0)