Which OpenShift resource provides TLS termination and external hostname exposure for an application?

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

Answer: (C)

Routes are the OpenShift resource that exposes an application to the outside world and handles TLS termination at the router. A Route lets you specify an external hostname (the host field) that clients will use to reach the app, and the OpenShift router terminates TLS on that connection, then forwards traffic to the backing service. This combination—external hostname exposure plus TLS termination at the edge—is what Routes provide in OpenShift.

In contrast, a LoadBalancer would provision an external load balancer, but TLS termination and host mapping are not defined by that resource alone. Ingress is a Kubernetes construct and not the native OpenShift mechanism for this scenario, and a ConfigMap is only for configuration data, not for exposing services.