What is the primary purpose of a Kubernetes Service in OpenShift?

What is the primary purpose of a Kubernetes Service in OpenShift?

• A. It stores container images.
• B. It defines deployment strategies.
• C. It provides stable networking and load balancing for a set of pods.
• D. It handles secrets.

Answer: (C)

A Kubernetes Service creates a stable network endpoint for a group of pods and distributes traffic among them. Pods can come and go or be recreated with new IPs, but the Service provides a fixed address (and DNS name) and uses a selector to route requests to all pods that match. This decouples clients from pod lifecycles and enables reliable access and basic load balancing across the set, which is essential for any scalable application. In OpenShift you can still expose that Service internally (ClusterIP) or externally (via NodePort, LoadBalancer, or a Route), but the core purpose remains providing stable networking and load balancing for the targeted pods. It isn’t responsible for storing images, defining deployment strategies, or managing secrets.

A Kubernetes Service creates a stable network endpoint for a group of pods and distributes traffic among them. Pods can come and go or be recreated with new IPs, but the Service provides a fixed address (and DNS name) and uses a selector to route requests to all pods that match. This decouples clients from pod lifecycles and enables reliable access and basic load balancing across the set, which is essential for any scalable application. In OpenShift you can still expose that Service internally (ClusterIP) or externally (via NodePort, LoadBalancer, or a Route), but the core purpose remains providing stable networking and load balancing for the targeted pods. It isn’t responsible for storing images, defining deployment strategies, or managing secrets.