What is the purpose of a Service in OpenShift, and how does it enable pod communication?

• A. A Service stores secrets for containers.
• B. A Service defines build steps for a container image.
• C. A Service provides a stable endpoint and load-balancing to a set of Pods.
• D. A Service is used to configure Routes.

Answer: (C)

In OpenShift, a Service provides a stable endpoint for a group of pods and handles distributing traffic among them. It uses a selector to identify the pods that belong to the service and creates a stable IP and DNS name that clients can use, so they don’t need to track individual pod IPs. The platform forwards requests to one of the healthy pods, effectively load-balancing across the set. This decouples clients from the ephemeral pod IPs, so communication remains reliable as pods are created, scaled, or replaced. The service is primarily for internal communication (ClusterIP by default), though it can be exposed externally via other mechanisms. Other options aren’t the purpose of a Service: secrets are managed by Secrets, build steps are defined by BuildConfig, and Routes expose services externally rather than define the service’s role.