A team keeps confusing two Kubernetes probe types. One probe decides whether a running container is healthy enough to keep, and when it fails repeatedly the kubelet restarts that container. The other probe decides whether a container is ready to receive traffic, and when it fails the container stays running but is removed from the Service endpoints. Which pairing correctly matches each behaviour to its probe?
- AThe restart-on-failure behaviour is the liveness probe, and the remove-from-endpoints behaviour is the readiness probe. Correct
- BThe restart-on-failure behaviour is the readiness probe, and the remove-from-endpoints behaviour is the liveness probe.
- CThe restart-on-failure behaviour is the startup probe, and the remove-from-endpoints behaviour is the liveness probe.
- DThe restart-on-failure behaviour is the readiness probe, and the remove-from-endpoints behaviour is the startup probe.
Why A is correct: A failing liveness probe causes the kubelet to restart the container, while a failing readiness probe leaves the container running but pulls it out of the Service endpoints so it receives no traffic, which is exactly the described split.
Why B is wrong: This reverses the two probes, which is a common mix-up, because readiness never restarts a container and liveness never merely deregisters an endpoint.
Why C is wrong: The startup probe only gates when the other probes begin and does not itself remove endpoints, and liveness restarts rather than deregisters, so neither half matches.
Why D is wrong: Readiness does not restart containers and the startup probe governs initial start-up timing rather than endpoint membership, so both descriptions are attached to the wrong probe.