HTTP rules on an Ingress work, but HTTPS for the listed host fails. kubectl shows the tls Secret name referenced by the Ingress does not exist. What is the likely diagnosis?
Select an answer to reveal the explanation.
Short Explanation
HTTP can still work while HTTPS is broken—the front desk answers on 80 but has no key for 443. A missing or wrong TLS Secret is the usual smoking gun. Fix or create that Secret and re-point tls.
Full Explanation
Ingress HTTP routing and TLS termination are related but separable. Controllers need a valid Secret for hosts listed under spec.tls; if it is missing or malformed, HTTPS fails even when HTTP backends work. Service types and readiness probe schemes are not the primary cause of that symptom, and missing Secrets do not rewrite Service types.