Diegolden

Topic 3: EndpointSlices And Discovery

2 min read

Topic 3: EndpointSlices And Discovery

Official baseline: (The Kubernetes Authors, 2026a, 2026b). My working version: EndpointSlices are the scalable backing list of where Service traffic can actually go.

Mental Model

EndpointSlices are the scalable backing list of where Service traffic can actually go.

Notes

  • A Service without ready endpoints is a routing contract with nowhere to route.
  • EndpointSlices expose readiness and topology details that help debugging.
  • Modern controllers should think in EndpointSlices, not only legacy Endpoints.

Homelab Angle

When a Service seems broken, inspect EndpointSlices before blaming DNS.

Verify It

  • Read the object status before changing the manifest.
  • Check events for the controller or node that is actually complaining.
  • Confirm the official source linked below still matches the cluster version you run.

Common Failure Modes

  • Treating the YAML object as the system, instead of one input to a reconciliation loop.
  • Debugging from outside the cluster when the failure only exists inside cluster networking or node state.
  • Forgetting that Kubernetes version, addon version, and runtime behavior are linked.

Sources

  • EndpointSlices - source path: content/en/docs/concepts/services-networking/endpoint-slices.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Service - source path: content/en/docs/concepts/services-networking/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.
The Kubernetes Authors. (2026a). EndpointSlices. https://kubernetes.io/docs/concepts/services-networking/endpoint-slices/
The Kubernetes Authors. (2026b). Service. https://kubernetes.io/docs/concepts/services-networking/service/

Graph View

Backlinks