You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Liveness and Readiness probes are pointing to the same endpoint, the effects of the probes are combined.
I think the title is correct, and the task body should be updated to reflect that it's generally fine to have the same endpoint called from liveness and readiness probes, as long as the values are different (and those for liveness are more tolerant than those for readiness).
if you use Liveness Probe, don’t set the same specification for Liveness and Readiness Probe
you can use a Liveness Probe with the same health check, but a higher failureThreshold (e.g. mark as not-ready after 3 attempts and fail Liveness Probe after 10 attempts)
The text was updated successfully, but these errors were encountered:
In Liveness probes values aren't the same as the Readiness:
I think the title is correct, and the task body should be updated to reflect that it's generally fine to have the same endpoint called from liveness and readiness probes, as long as the values are different (and those for liveness are more tolerant than those for readiness).
Referenced article Liveness probes are dangerous:
The text was updated successfully, but these errors were encountered: