github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-03 17:30:00 +00:00
Code Issues Projects Releases Wiki Activity

Fix doc typos

Browse Source
This commit is contained in:
Janet Kuo 2015-07-22 17:16:28 -07:00
parent d9bb171f8a
commit a2971fb2ab
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/admin/networking.md
View File

@ -125,7 +125,7 @@ applies IP addresses at the `Pod` scope - containers within a `Pod` share their
network namespaces - including their IP address. This means that containers 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 that processes in a VM. We call this the "IP-per-pod" model. This different than processes in a VM. We call this the "IP-per-pod" model. This
is implemented in Docker as a "pod container" which holds the network namespace is implemented in 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.

2
docs/design/networking.md
View File

@ -87,7 +87,7 @@ whereas, in general, they don't control what pods land together on a host.
## Pod to pod ## Pod to pod
Because every pod gets a "real" (not machine-private) IP address, pods can Because every pod gets a "real" (not machine-private) IP address, pods can
communicate without proxies or translations. The can use well-known port communicate without proxies or translations. The pod can use well-known port
numbers and can avoid the use of higher-level service discovery systems like numbers and can avoid the use of higher-level service discovery systems like
DNS-SD, Consul, or Etcd. DNS-SD, Consul, or Etcd.