How does a Route work in OpenShift, and what TLS termination options are available?

• A. Route exposes an internal service only within the cluster.
• B. Route exposes a service to external clients; TLS termination options include edge, reencrypt, and passthrough.
• C. Route is used to configure persistent storage.
• D. Route creates a new deployment.

Answer: (B)

A Route in OpenShift is used to expose a service to external clients, providing a hostname and rules that tell the cluster’s router how to send traffic from outside to the internal service.

TLS termination options indicate where the secure connection is terminated and how encryption is handled between the router and the backend:

• Edge termination: the TLS handshake ends at the router. The router decrypts the client traffic and forwards it to the service, typically over HTTP. The router supplies the certificate that clients connect to.

• Reencrypt termination: TLS ends at the router, but the router then re-encrypts traffic and sends it to the backend, using another certificate for the backend connection. This keeps end-to-end encryption between client and service, with the router handling TLS on both sides.

• Passthrough termination: the TLS connection is not terminated at the router at all; the client’s TLS traffic goes straight through to the backend, and the service handles TLS itself.

So, a Route exposes a service to external clients, and you can choose how TLS is handled: at the edge (router), reencrypted to the backend, or passed through to the backend.