An Ingress must terminate HTTPS for permits.example.gov using certificate files you already have. Which Secret approach fits Ingress TLS?
Select an answer to reveal the explanation.
Short Explanation
Ingress HTTPS wants a proper TLS Secret—cert and key as tls.crt and tls.key. Point spec.tls at that Secret for the host. Username/password Opaque Secrets and ConfigMaps aren't the Ingress TLS handshake material.
Full Explanation
Ingress TLS commonly references a Secret of type kubernetes.io/tls containing tls.crt and tls.key. The Ingress spec.tls[].secretName (with hosts) wires that material to the controller for HTTPS. Opaque login Secrets, ConfigMaps, and annotation-only PEM storage are not the standard Ingress certificate mechanism.