Merge pull request #34457 from chetak123/change_grep

updated grep with custom-columns=POD_IP:.status.podIPs

Author: k8s-ci-robot

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

@@ -45,9 +45,10 @@ my-nginx-3800858182-kna2y   1/1       Running   0          13s       10.244.2.5
 Check your pods' IPs:
 
 ```shell
-kubectl get pods -l run=my-nginx -o yaml | grep podIP
-    podIP: 10.244.3.4
-    podIP: 10.244.2.5
+kubectl get pods -l run=my-nginx -o custom-columns=POD_IP:.status.podIPs
+    POD_IP
+    [map[ip:10.244.3.4]]
+    [map[ip:10.244.2.5]]
 ```
 
 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.