Service backend
Whatever actually answers the traffic a Service, Ingress or route forwards: the ready pods behind a Service, or the Service an Ingress rule points at.
In more detail
An Ingress rule or HTTPRoute names a backend Service, and that Service in turn sends traffic to its ready pods. An empty set of backends means requests have nowhere to go, which shows up as timeouts or errors even when DNS works. EndpointSlices list the ready backends of a Service.
Related terms
- Kubernetes Service — The Kubernetes object that gives a changing set of pods one stable name and address, and spreads traffic across the ready ones.
- EndpointSlice — The object that lists the actual pod addresses behind a Service and whether each one is ready.
- Ingress — A Kubernetes object that describes how outside HTTP traffic reaches services inside the cluster, by host name and URL path.
- HTTPRoute — The Gateway API object an application team writes to route HTTP requests by host, path or header from a Gateway to its Services.
Taught in
- Slow, Or Broken? Metrics, Logs And Traces — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Who Decides What Ships: The CNCF And Its Community — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- ClusterIP, Selectors, EndpointSlices And DNS — Kubernetes: Production-Grade Container Orchestration
- Ingress: Controllers, Hosts, Paths And TLS — Kubernetes: Production-Grade Container Orchestration
- Gateway API: GatewayClass, Gateway And HTTPRoute — Kubernetes: Production-Grade Container Orchestration
- NetworkPolicy And The Consul Service Mesh Boundary — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: DNS, Empty Endpoints And Broken Routes — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: A Timed Service Recovery Drill — Kubernetes: Production-Grade Container Orchestration