A city open-data API exposes HTTP health on path /healthz at container port 8080. How should an httpGet probe be configured?
Select an answer to reveal the explanation.
Short Explanation
The probe has to knock on the door the app actually opened. Point httpGet at /healthz on port 8080—the same path and port the service uses for health. Wrong path, wrong port, or checking something outside the Pod won’t tell you if this container is ready.
Full Explanation
HTTP probes must match the application’s real health URL and listening port. For an API that serves /healthz on 8080, configure httpGet.path accordingly and set port to 8080 (or the matching named port). Probing / on 80, SSH, or an external SaaS page does not validate this container’s health endpoint.