What is the purpose of a Service in OpenShift?

• A. A Service provides a stable endpoint and load balancing for a set of Pods selected by labels.
• B. A Service stores configuration data for applications.
• C. A Service defines storage volumes for pods.
• D. A Service runs as a daemon on each node.

Answer: (A)

A Service provides a stable endpoint and load balancing for a group of Pods selected by labels. Pods come and go as deployments scale or roll out updates, but the Service exposes a single, stable address (IP and DNS name) that clients can use regardless of the pod lifecycle. It uses a label selector to identify which pods belong to the service, and maintains an Endpoints list so traffic can be balanced across all healthy pods in that group. Depending on how you configure it, the service address can be used inside the cluster or exposed externally via additional types like NodePort or LoadBalancer. This mechanism enables reliable service discovery and consistent routing for clients and other services.

Storing configuration data is handled by ConfigMaps and Secrets, not by a Service. Defining storage volumes is done with PersistentVolumes and PersistentVolumeClaims. Running a daemon on every node is typically done with a DaemonSet, not a Service.