Hands-on Lab·Certified Kubernetes Administrator
EndpointSlices in Detail
Where a Service's backend list actually lives, the three conditions each address carries, and a side-by-side comparison with the object EndpointSlices replaced.
Services and Networking Guide 49 of 103 Intermediate
- Kubernetes1.36.4
- Cluster4 nodes
- Runtimecontainerd 2.2.6
- CNICalico v3.32.1
- TimeAbout 15 min
v1 Endpoints is deprecated from 1.33. It is still populated for compatibility, which is what makes the comparison in step three possible.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE01 | 192.168.0.176 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE02 | 192.168.0.177 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE03 | 192.168.0.178 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
This guide includes
Use this when you have to say exactly why a Service is or is not sending traffic to a particular Pod. This matters because each address carries three separate conditions, and only reading them tells you whether a Pod is being skipped, drained, or still served.
- finding where a Service's backend list actually lives, since the Service itself does not hold it
- reading the three conditions each address carries rather than the single one people expect
- breaking readiness and comparing the same failure through both the Endpoints and EndpointSlice APIs
- seeing the slice owned by the Service, so deleting one garbage-collects the other
Before you start
- guide 48 - the overview, before this reads the object field by field.
-
What a Service actually points at
-
What is inside a slice
-
Break readiness and compare the two objects
-
The shape of the object itself