Module 6
Networking
Kubernetes defines a simple flat network model and delegates the work to a plugin. On top of it, Services give stable names, DNS makes them discoverable, and policies restrict who may talk.
Why it matters. Almost every connectivity incident is one of: a Service with no endpoints, a DNS problem, a NetworkPolicy, or an Ingress or Gateway misconfiguration. Knowing the layers makes each one a short checklist.
After this module you can answer
- What are the ground rules of the Kubernetes network?
- Why do Pods need Services at all?
- What are the four Service types, and what is a headless Service?
- How does a name like checkout.shop resolve?
- Why is a NetworkPolicy useless on some clusters?
What is inside
1Model and CNI
2Services
3Headless and EndpointSlices
4DNS
5NetworkPolicy
6Ingress and Gateway API
7Request journey
8Module infographic