Skip to content

Commit 7ad4627

Browse files
authored
Merge pull request #25418 from bl-ue/patch-1
Containers in a pod share their MAC address
2 parents bc72bf3 + 5f59529 commit 7ad4627

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

content/en/docs/concepts/cluster-administration/networking.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,10 +58,11 @@ to containers. If your job previously ran in a VM, your VM had an IP and could
5858
talk to other VMs in your project. This is the same basic model.
5959

6060
Kubernetes IP addresses exist at the `Pod` scope - containers within a `Pod`
61-
share their network namespaces - including their IP address. This means that
62-
containers within a `Pod` can all reach each other's ports on `localhost`. This
63-
also means that containers within a `Pod` must coordinate port usage, but this
64-
is no different from processes in a VM. This is called the "IP-per-pod" model.
61+
share their network namespaces - including their IP address and MAC address.
62+
This means that containers within a `Pod` can all reach each other's ports on
63+
`localhost`. This also means that containers within a `Pod` must coordinate port
64+
usage, but this is no different from processes in a VM. This is called the
65+
"IP-per-pod" model.
6566

6667
How this is implemented is a detail of the particular container runtime in use.
6768

0 commit comments

Comments
 (0)