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

Update networking.md (#7578) 

Clarified 'pod container' description.
pull/6964/head^2
the0ffh 2018-03-03 20:42:53 +01:00 committed by k8s-ci-robot
parent 46d896e518
commit 550c26b929
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/concepts/cluster-administration/networking.md
View File

@ -85,7 +85,7 @@ network namespaces - including their IP address. This means that containers
within a `Pod` can all reach each other's ports on `localhost`. This does imply within a `Pod` can all reach each other's ports on `localhost`. This does imply
that containers within a `Pod` must coordinate port usage, but this is no that containers within a `Pod` must coordinate port usage, but this is no
different than processes in a VM. This is called the "IP-per-pod" model. This different than processes in a VM. This is called the "IP-per-pod" model. This
is implemented in Docker as a "pod container" which holds the network namespace is implemented, using Docker, as a "pod container" which holds the network namespace
open while "app containers" (the things the user specified) join that namespace open while "app containers" (the things the user specified) join that namespace
with Docker's `--net=container:<id>` function. with Docker's `--net=container:<id>` function.