Which probes determine if a pod is ready to receive traffic and if it is alive?

Which probes determine if a pod is ready to receive traffic and if it is alive?

• A. ReadinessProbe and LivenessProbe
• B. StartupProbe and ReadinessProbe
• C. LivenessProbe and StartupProbe
• D. HealthProbe and ReadinessProbe

Answer: (A)

Understand how probes relate to serving traffic and keeping containers healthy. A pod is considered ready to receive traffic based on its readiness probe. If the readiness check passes, the pod’s endpoints are included in the service, and it can receive requests. The liveness probe, on the other hand, watches for an unhealthy or unresponsive container; if the liveness check fails, Kubernetes restarts that container to recover. So, the combination of readiness and liveness probes answers both questions: is the pod ready to handle traffic now, and is the container still alive and healthy? StartupProbe exists to help with slow-start scenarios, but it’s not about traffic readiness or ongoing liveness.

Understand how probes relate to serving traffic and keeping containers healthy. A pod is considered ready to receive traffic based on its readiness probe. If the readiness check passes, the pod’s endpoints are included in the service, and it can receive requests. The liveness probe, on the other hand, watches for an unhealthy or unresponsive container; if the liveness check fails, Kubernetes restarts that container to recover.

So, the combination of readiness and liveness probes answers both questions: is the pod ready to handle traffic now, and is the container still alive and healthy? StartupProbe exists to help with slow-start scenarios, but it’s not about traffic readiness or ongoing liveness.