A Service's selector is not what kube-proxy actually uses. The EndpointSlice controller evaluates the selector and writes the matching Pods' IPs and ports into EndpointSlice objects, and kube-proxy, DNS and ingress controllers consume those. EndpointSlices replaced the older Endpoints API, which could not scale to very large Services because one object held every address.
Free account
Keep reading for free
Create a free StudyToCert account to read the rest of this lesson: 6 more sections, 4 key terms, a real-world example, an exam tip and self-check questions. Every lesson, lab and practice test is free with an account.