A health check is an endpoint-based diagnostic that reports whether a deployed service or pod is functioning and able to handle requests. In Kubernetes environments, it supports observability, pod management, and troubleshooting. section 10.4.1
Distinguish the related checks by the operational decision they support:
- Liveness probes call /healthz periodically to determine whether the pod is alive and able to run its main process; failure may cause Kubernetes to restart it. section 10.4.1
- Readiness probes call /readyz periodically to determine whether the pod is operational and ready to receive traffic. section 10.4.1
- BentoML provides built-in health checks and liveness/readiness probe support, reducing the endpoint implementation required for a deployed service. section 10.4.1
Diagnosing a pod that will not initialize
Configure Kubernetes to inspect /healthz for liveness and /readyz for readiness. A failing /healthz indicates an initialization or process problem to investigate; a pod that is alive but not ready should not receive traffic. section 10.4.1
Figure 10.7 BentoML’s built-in observability endpoints for K8s environments
Inspect the BentoML observability endpoints supplied for Kubernetes environments. section 10.4.1








