Building-permits needs HTTPS termination on a Gateway listener using a certificate already stored in the cluster. What configuration approach fits Gateway API?
Select an answer to reveal the explanation.
Short Explanation
Put the lock on the front door: terminate TLS on the Gateway listener and point it at the certificate Secret. That keeps HTTPS at the shared entrypoint instead of stuffing keys into random ConfigMaps or route annotations.
Full Explanation
Gateway listeners can be configured for TLS termination and typically reference Kubernetes Secrets that hold the certificate material. Central listener TLS is the usual pattern for shared municipal entrypoints. Hiding keys in ConfigMaps or annotations is incorrect; while apps can also do TLS, Gateway API’s listener TLS support is specifically for edge termination with referenced Secrets.