1 - yes, containers are left there forever. Think of readiness probe as a breaker, if the app gets overwhelmed it cuts the traffic to the pod until it's ready to get traffic again.
2 - no, by itself, readiness probes only stop/start traffic to a pod. To signal kubernetes that the pod needs to be restarted use liveness probes.
3 - yes, as per answer 1. Readiness probes are a way of letting kubernetes know that the pod can handle traffic or if they need a break.
probe: startup probes - waits for the app to start
use case: apps that need some time before start serving traffic, for example, building assets on start, pre-fetching assets, building caches, etc.
liveness probes - checks if the app is healthy
use case: check if the app is running, if the app has exited due to an exception and needs to be restarted, or if the app is running but can't serve requests
readiness probes - checks if the app can handle traffic
use case: apps that can arbitrarily stop receiving traffic, e.g. maintenance mode, data intensive apps that can degrade in performance and need a way to
You should use liveness and readiness probes always, use startup probes when your app takes more time than usual to start.
- python app with postgres database:
- liveness probe: get /health status 200
- readiness probe: get /health status 200, timeout 1s
the /health endpoint queries the database using a simple query (select id, email from user limit 1) and returns a json
if the pod loses connectivity to the database, the liveness probe will fail and the pod will be restarted.
if the database is being overwhelmed by requests, the query will take more than 1s, the probe will mark the pod as not ready, preventing that additional requests reach the database and preventing it from progressing from overwhelmed to crashed. once the database is able to catch up and starts returning queries in less than 1s, readiness probe will mark the pod as healthy again and kubernetes will resume serving requests to the pod.