To enable external access to an application, which OpenShift object should be configured to map a hostname to the service?

To enable external access to an application, which OpenShift object should be configured to map a hostname to the service?

• A. Route
• B. Ingress
• C. Service
• D. ConfigMap

Answer: (A)

OpenShift exposes applications to the outside world by using a Route that maps a DNS hostname to a backend service inside the cluster. The Route ties an externally reachable host (and optionally a path) to a specific service and port, letting the OpenShift router forward incoming requests for that host to the appropriate pods. You can also configure TLS on the Route if you need encrypted traffic. The Service provides the internal destination for traffic, but it’s Route that bridges external hostname access to that service. ConfigMap is for configuration data and isn’t involved in routing, and while Ingress exists in Kubernetes, OpenShift’s established method for mapping a hostname to a service is the Route.

OpenShift exposes applications to the outside world by using a Route that maps a DNS hostname to a backend service inside the cluster. The Route ties an externally reachable host (and optionally a path) to a specific service and port, letting the OpenShift router forward incoming requests for that host to the appropriate pods. You can also configure TLS on the Route if you need encrypted traffic. The Service provides the internal destination for traffic, but it’s Route that bridges external hostname access to that service. ConfigMap is for configuration data and isn’t involved in routing, and while Ingress exists in Kubernetes, OpenShift’s established method for mapping a hostname to a service is the Route.