When configuring TLS for an OpenShift Route, which Route field references the TLS secret?

Prepare for the Red Hat Openshift Developer EX288 Exam. Study with comprehensive quizzes and flashcards. Each question includes hints and explanations to enhance your understanding. Ace your exam with confidence!

Multiple Choice

When configuring TLS for an OpenShift Route, which Route field references the TLS secret?

Explanation:
OpenShift Route TLS termination is configured by pointing the Route to a Kubernetes Secret that holds the certificate and key. The field you use for this is spec.tls.secret. This tells the router which secret in the same namespace contains the TLS material (certificate and private key) used to terminate TLS for that route. The secret referenced here is created as a standard TLS secret (typically containing tls.crt and tls.key) and is looked up by the router when handling traffic for the route. Other options presented aren’t actual fields on a Route for referencing TLS secrets, so they don’t apply. For example, you might see a Route with spec.tls.termination set to edge and spec.tls.secret set to my-tls-secret to indicate which secret to use.

OpenShift Route TLS termination is configured by pointing the Route to a Kubernetes Secret that holds the certificate and key. The field you use for this is spec.tls.secret. This tells the router which secret in the same namespace contains the TLS material (certificate and private key) used to terminate TLS for that route. The secret referenced here is created as a standard TLS secret (typically containing tls.crt and tls.key) and is looked up by the router when handling traffic for the route. Other options presented aren’t actual fields on a Route for referencing TLS secrets, so they don’t apply. For example, you might see a Route with spec.tls.termination set to edge and spec.tls.secret set to my-tls-secret to indicate which secret to use.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy