health-checks

Kubernetes liveness and readiness probes are implemented by configuring your deployment to use specific endpoints, such as `/health/live` for liveness and `/health/ready` for readiness, ensuring traffic is only routed to fully operational application instances.

A liveness probe detects if a process is running and responsive, while a readiness probe determines if an application is ready to serve traffic, ensuring new versions are only rolled out when the application is fully prepared.

Dependency health checks are implemented by defining specific check functions for services like databases, caches, and external APIs to monitor and report their operational status, ensuring infrastructure reliability.

Yes, the health check framework supports both TypeScript and Python applications, allowing you to implement liveness, readiness, and dependency check endpoints for Kubernetes probes and load balancers in either environment.

Dependency health checks are needed when your application relies on critical external services like databases or caches, allowing monitoring systems to accurately report operational status and automatically restart unhealthy instances.

Pods restart prematurely when readiness probes are not configured to use an endpoint like `/health/ready`, causing Kubernetes to assume the application is ready before critical dependencies are fully operational and serving traffic.