[id="understanding-networking"]
= Understanding networking
include::modules/common-attributes.adoc[]
:context: understanding-networking

toc::[]

Kubernetes ensures that Pods are able to network with each other, and allocates
each Pod an IP address from an internal network. This ensures all containers
within the Pod behave as if they were on the same host. Giving each Pod its own
IP address means that Pods can be treated like physical hosts or virtual
machines in terms of port allocation, networking, naming, service discovery,
load balancing, application configuration, and migration.

include::modules/nw-ne-openshift-dns.adoc[leveloffset=+1]

[id="understanding-networking"]
= Understanding networking
include::modules/common-attributes.adoc[]
:context: understanding-networking

toc::[]

Kubernetes ensures that Pods are able to network with each other, and allocates
each Pod an IP address from an internal network. This ensures all containers
within the Pod behave as if they were on the same host. Giving each Pod its own
IP address means that Pods can be treated like physical hosts or virtual
machines in terms of port allocation, networking, naming, service discovery,
load balancing, application configuration, and migration.

[NOTE]
====
Some cloud platforms offer metadata APIs that listen on the 169.254.169.254 IP address, a link-local IP address in the IPv4 `169.254.0.0/16` CIDR block.

This CIDR block is not reachable from the pod network. Pods that need access to these IP addresses must be given host network access by setting the `spec.hostNetwork` field in the Pod spec to `true`.

If you allow a Pod host network access, you grant the Pod privileged access to the underlying network infrastructure.
====

include::modules/nw-ne-openshift-dns.adoc[leveloffset=+1]

Add note about link-local IP addresses
Add note about link-local IP addresses

- https://bugzilla.redhat.com/show_bug.cgi?id=1718389
