⎈ k8s knowledge compiler
k8s / Docs / EndpointSlice

EndpointSlice [glossary]deterministic

EndpointSlices track the IP addresses of Pods for Services.

networking

EndpointSlices track the IP addresses of backend endpoints. EndpointSlices are normally associated with a [Service](#gloss:service) and the backend endpoints typically represent [Pods](#gloss:pod).

One Service can be backed by multiple Pods. Kubernetes represents the backing endpoints of a Service with a set of EndpointSlices that are associated with that Service. The backing endpoints are usually, but not always, pods running in the cluster.

The control plane usually manages EndpointSlices for you automatically. However, EndpointSlices can be defined manually for [Services](#gloss:service) without [selectors](#gloss:selector) specified.

Sources

reference/glossary/endpoint-slice.md · doc — “EndpointSlices track the IP addresses of Pods for Services.”

Related (11)

references Debugging DNS Resolution — endpointslice conf=1
references API-initiated Eviction — EndpointSlice conf=1
defines EndpointSlices conf=1
references Service — EndpointSlices conf=1
references DNS for Services and Pods — EndpointSlice conf=1
references Pod Lifecycle — EndpointSlice conf=1
references Liveness, Readiness, and Startup Probes — EndpointSlice conf=1
references Connecting Applications with Services — EndpointSlices conf=1
references Virtual IPs and Service Proxies — EndpointSlice conf=1
references What Happens After A Node Restart — EndpointSlices conf=1
prerequisite_of CustomResourceDefinition — ai-suggested prerequisite conf=0.7

← all Docs