Kubernetes - Readiness Probe execution after container started

Viewed 4148

Is there a way to prevent readiness probe from execution once container has successfully started? I suppose that liveness probe should be enough to monitor container health.

2 Answers

This problem should be now addressed with Startup probes.

The startup probe is called during startup and is used to determine when the container is ready to accept requests. If a startup probe is configured, the liveness and readiness checks are disabled until the startup probe succeeds.

Startup probes can be set at an aggressive pace to ensure that your application is available as soon as possible.

Readiness probe can be set at a less aggressive pace to handle "backlog" like situations mentioned in the accepted answer.

And Liveness probe when you need a pod restart.

Related