A multi-container Pod has a main city-maps API and a log-shipping sidecar. Probes were attached only to the sidecar, which never serves /healthz. What should the developer fix?
Select an answer to reveal the explanation.
Short Explanation
Probes live on a specific container, not ‘the Pod in general.’ If /healthz is on the maps API, put the probe on that container—not on the log sidecar. Wrong target means you’re checking the neighbor’s doorbell.
Full Explanation
Each container in a Pod has its own probe fields. Health checks must be defined on the container that listens for the probed protocol and path. Probing a sidecar that does not serve the application health endpoint yields misleading failures or false passes. Probes are not specified at an abstract Pod-wide root independent of containers.