kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update connect-applications-service.md 

We are talking about pods here, not about services yet.
pull/42085/head
Alex Serbul 2023-07-19 13:16:49 +03:00 committed by GitHub
parent 52132d2af2
commit 8face3d008
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/tutorials/services/connect-applications-service.md
View File

@ -59,7 +59,7 @@ to make queries against both IPs. Note that the containers are *not* using port
the node, nor are there any special NAT rules to route traffic to the pod. This means 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`, 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 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 address for the pod. 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 Node to be forwarded to backing Pods, you can - but the networking model should
mean that you do not need to do so. mean that you do not need to do so.