A reverse-proxy sidecar must read a TLS certificate and key as files under /certs. Which consumption pattern fits?
Select an answer to reveal the explanation.
Short Explanation
TLS material likes being files on disk, not one giant env string. Mount the Secret as a volume and the keys show up as files under /certs. That's the usual pattern for cert and key paths.
Full Explanation
Secrets mounted as volumes project each key as a file in the mount path, which suits TLS certificate and private key consumption. ConfigMaps should not hold private keys, comma-separated env blobs are fragile for PEM material, and annotations are not a secure or standard delivery mechanism for key pairs.