Configure Liveness, Readiness and Startup Probes
wardvandriessche-centrica opened this issue · comments
It is not clear from the documentation which ServiceStatus fields are used from the gRPC Health Check Protocol and also if it's possible to customize.
For example: is it possible to set up the liveliness/readiness probes in such a way that a SERVING response is considered "ready" and a SERVING or NOT_SERVING is considered "alive". An UNKNOWN response would then fail both ready and alive.
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
Page reported in issue (based on issue title): https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
/language en