In Kubernetes, which object represents the endpoints backing a Service?

Study for the Kubernetes Certified Network Administrator Exam. Our test offers comprehensive flashcards, multiple-choice questions, and detailed explanations. Be confident for your exam!

Multiple Choice

In Kubernetes, which object represents the endpoints backing a Service?

Explanation:
The mapping from a Service to the actual back-end pods is held in an Endpoints object. When a Service selects pods by labels, Kubernetes populates Endpoints with the IP addresses and ports of those pods. This Endpoints data is what the cluster’s proxy uses to route traffic to the correct pods. A Pod is the workload itself, not the representation of the back-end addresses for a Service. A Node is simply the host where pods run, not the set of addresses backing a Service. The Service provides a stable front end, while Endpoints lists the actual Pod endpoints behind it. (Note: EndpointSlices serve the same purpose in newer designs for scalability, but Endpoints is the traditional backing store.)

The mapping from a Service to the actual back-end pods is held in an Endpoints object. When a Service selects pods by labels, Kubernetes populates Endpoints with the IP addresses and ports of those pods. This Endpoints data is what the cluster’s proxy uses to route traffic to the correct pods. A Pod is the workload itself, not the representation of the back-end addresses for a Service. A Node is simply the host where pods run, not the set of addresses backing a Service. The Service provides a stable front end, while Endpoints lists the actual Pod endpoints behind it. (Note: EndpointSlices serve the same purpose in newer designs for scalability, but Endpoints is the traditional backing store.)

More Multiple Choice Questions
Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy