k8s-debug

Diagnose CrashLoopBackOff and OOMKilled pods by running a script-driven pod diagnostics workflow that collects structured evidence across application logs, resource limits, and configuration layers to pinpoint the root cause safely.

Troubleshoot Kubernetes DNS resolution failures by running focused network and DNS diagnostic scripts that inspect CoreDNS health and network policies, mapping vague connectivity complaints into an evidence-driven investigation path.

Fix ImagePullBackOff and Pending states by identifying the problem layer through preflight checks and targeted kubectl diagnostics, determining whether the failure stems from image authentication, resource pressure, or node scheduling constraints.

You can investigate stuck rollouts and PVC mount problems by collecting cluster health snapshots and storage diagnostics, applying safety guardrails that require rollback planning before executing any disruptive kubectl operations.

You need kubectl access to the active context to troubleshoot Kubernetes workload failures, allowing the diagnostic scripts to gather pod, service, node, and storage layer evidence without requiring elevated cluster-admin privileges.

Kubernetes pod diagnostics require a structured workflow to prevent destructive actions, ensuring you collect baseline evidence and create snapshot or rollback plans before applying targeted fixes that could impact the active cluster state.