In Kubernetes, what are Service Endpoints primarily used for?

• A. Listing the available namespaces
• B. Scheduling Pods on nodes
• C. Tracking the IP addresses and ports of Pods associated with a Service
• D. Managing persistent volume claims

Answer: (C)

Service Endpoints are the dynamic mapping of a Service to the actual backend pods, listing the IP addresses and ports of the pods that back the Service. This mapping is what kube-proxy uses to route traffic to the correct pods behind the Service, so clients can reach the service via a stable IP or DNS name while the underlying pods may scale up or down. The Endpoints object is maintained by the Endpoint controller and updated as pods come and go or change readiness, ensuring the routing information stays in sync with the current backends. If a Service uses a selector, Endpoints are automatically populated with the pods matching that selector; you can also configure endpoints manually if needed. The other options don’t describe this backend-mapping role: listing namespaces, scheduling pods, and managing persistent volumes are handled by different parts of Kubernetes.