Checks if the current epoch of the node is not too far behind the network.
Making the threshold too strict can cause the node to repeatedly report as not ready, especially
in case of forking.
This endpoint is a combination of the [livez]
and [readyz]
endpoints, except that the node
doesnβt have to be fully synced. Deprecated in the Kubernetes world, but still used in some setups.
Liveness probes determine whether or not an application running in a container is in a healthy state. The idea behind a liveness probe is that it fails for prolonged period of time, then the application should be restarted.
In our case, we require:
Readiness probes determine whether or not a container is ready to serve requests.
The goal is to determine if the application is fully prepared to accept traffic.
In our case, we require: