health-checks

Optimize Kubernetes liveness, readiness, and startup probe configurations.

Updated Jun 5, 2026

Search Tags:#kubernetes #health checks #distributed systems #reliability #probe configuration

Ready to run

npx skills add https://github.com/hung-phan/system-skills --skill health-checks-hung-phan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: health-checks
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/reliability/health-checks
Command: npx skills add https://github.com/hung-phan/system-skills --skill health-checks-hung-phan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common pitfalls of Kubernetes health probes (liveness, readiness, startup) that can cause cascading failures and misinform resource management, leading to outages and slow recovery.

Core Features & Use Cases

Separates Liveness, Readiness, Startup Probes: Guides configuration to avoid mixing probe types and their consequences.
Deep Health Checks with Observability: Provides patterns for running dependency checks that don't trigger direct resource drain.
Trapdoor Failure Prevention: Advises on mitigating lock-step failure scenarios by keeping minimum healthy targets.
Use Case: Apply this when optimizing your Kubernetes deployment configurations for stability, preventing healthy pods from being killed, and ensuring dependency failures don't cause widespread service outages.

Quick Start

Configure a Kubernetes Deployment using the patterns described for liveness, readiness, and deep health probes to prevent cluster-wide failures.

Frequently Asked Questions about health-checks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why do my Kubernetes liveness probes cause cascading failures across my distributed system?▼

Kubernetes liveness probes cause cascading failures when they check dependencies directly, amplifying lock-step failures. Separating liveness, readiness, and startup probe purposes prevents healthy pods from being killed during downstream outages.

How do I configure Kubernetes startup probes to prevent killing healthy pods?▼

Configure Kubernetes startup probes to validate initial initialization without mixing in dependency checks. This separates startup from liveness probing, preventing premature pod termination and ensuring reliable service availability during slow boot sequences.

What is the difference between liveness and readiness probe configuration for reliable service availability?▼

Liveness probe configuration checks if a pod needs restarting, while readiness probe configuration determines if it receives traffic. Mixing these Kubernetes health checks misinforms resource management and triggers widespread service outages.

How do I run deep health checks in Kubernetes without triggering direct resource drain?▼

Run deep health checks with observability patterns that report dependency status without linking to pod termination logic. This prevents Kubernetes from killing healthy pods when external dependencies fail, avoiding direct resource drain.

How do I prevent lock-step failure amplification in Kubernetes probe configuration?▼

Prevent lock-step failure amplification in Kubernetes probe configuration by keeping minimum healthy targets and avoiding synchronized dependency checks. Distinct probe purposes mitigate cascading trapdoor failure scenarios across distributed systems.

When should I not use Kubernetes liveness probes for dependency monitoring?▼

Avoid using Kubernetes liveness probes for dependency monitoring when downstream services are unstable. Coupling liveness to dependencies causes healthy pods to be killed, creating trapdoor failures and cascading outages across the cluster.