Diegolden

Services, Networking And DNS

2 min read

Services, Networking And DNS

Networking is the part of Kubernetes where names, identity, routing, and policy meet. Most homelab confusion lives here.

Topics

  • Kubernetes Network Model - Kubernetes assumes Pods can talk to Pods without NAT. The CNI implementation makes that promise real.
  • Services - A Service is a stable contract over unstable Pods: name, virtual IP, and selection rules.
  • EndpointSlices And Discovery - EndpointSlices are the scalable backing list of where Service traffic can actually go.
  • DNS - DNS turns Kubernetes objects into names humans and applications can depend on.
  • Ingress And Gateway API - Ingress and Gateway API are traffic management layers above Services. They decide how external HTTP traffic reaches internal backends.
  • NetworkPolicy - NetworkPolicy is a firewall model for Pods, but only if the network plugin enforces it.

Editorial Notes

  • Keep the official docs as the citation layer.
  • Keep this lab opinionated around homelab operations: verification, failure modes, and practical boundaries.
  • Avoid copying upstream prose; cite it, then explain the operating model in our own language.

Sources

  • Services, Load Balancing, and Networking - source path: content/en/docs/concepts/services-networking/_index.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Service - source path: content/en/docs/concepts/services-networking/service.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • DNS for Services and Pods - source path: content/en/docs/concepts/services-networking/dns-pod-service.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Kubernetes documentation is licensed under CC BY 4.0; these notes are original commentary and link back to the official source.

6 items under this folder.