A product owner wants automatic HTTP to HTTPS redirects for an Ingress. Which statement reflects correct CKAD-level expectations?
Select an answer to reveal the explanation.
Short Explanation
Want HTTP bumped to HTTPS? That is usually a controller knob or annotation, not a secret core field named redirectHttp. Do not invent YAML that the API never had.
Full Explanation
When a product owner wants automatic HTTP to HTTPS redirects for an Ingress, the correct CKAD-level expectation is that redirect behavior is often provided by controller-specific annotations or settings; do not invent a nonexistent core Ingress field that claims to force redirects. Core Ingress specifies hosts, paths, pathTypes, backends, and tls Secret references. Redirects from HTTP to HTTPS are commonly implemented via annotations (for example on nginx Ingress controllers) or controller config—not a universal portable core field.
spec.tls.redirectHttp: true is not a core field on every Ingress since early Kubernetes. Service.type RedirectHTTPS does not exist as a cluster-wide HTTP upgrade mechanism. Enabling redirects by deleting the http rules block and keeping only tls hosts breaks HTTP routing configuration rather than performing a proper redirect.
Exam caveat: if an exam environment documents a redirect annotation, use that annotation; otherwise explain that redirects are controller-specific extras. Operational check: apply the controller’s approved redirect annotation or configuration, curl -I http://host and expect a 301/302 to https, then follow to the civic site on HTTPS. Document the approved approach in city platform standards so teams do not invent fake Ingress fields in GitOps.