Which Kubernetes component is responsible for exposing applications running on a set of Pods as a network service?

• A. A load balancer device
• B. Ingress
• C. Service
• D. Pod

Answer: (C)

A Service is the Kubernetes construct that exposes applications running on a set of Pods as a network service. It provides a stable endpoint (a ClusterIP by default, and optionally a DNS name) and, using label selectors, forwards traffic to the Pods that back the service. Kubernetes keeps track of the current set of Pod endpoints and the underlying kube-proxy rules route requests to one of the healthy Pods, effectively load-balancing among them. This separation lets clients reach the app without needing to know which Pod instances are running or their IPs, and it remains stable even as Pods come and go.

Ingress handles HTTP(S) routing at a higher level and relies on Services to reach the actual backends, so it’s not the direct mechanism for exposing a set of Pods as a service. A Pod itself is the runtime unit, not a stable network endpoint for external access. A load balancer device can be used in front of a Service of type LoadBalancer, but the fundamental Kubernetes resource that exposes the set of Pods as a network service is the Service.