debug_k8s

To debug Kubernetes pods in CrashLoopBackOff or Pending states, you can run guided kubectl checks to inspect pod statuses, retrieve container logs, and review cluster events to identify root causes and next steps.

Checking Kubernetes pod health involves inspecting current pod statuses, conditions, and restart counts to identify stability issues, which this diagnostic process gathers using safe, read-only kubectl commands.

Gathering Kubernetes logs and events requires retrieving recent container logs and cluster events to surface root causes and timing, providing actionable remediation steps for failing deployments.

Yes, you can inspect cluster state by describing related deployments, services, and configurations using safe, read-only kubectl commands via Gemini CLI to investigate issues without modifying the cluster.

Yes, you need to provide the namespace and the specific resource name, such as a pod, deployment, or service, to run targeted kubectl checks for status, logs, and events.

Diagnosing Kubernetes issues with kubectl involves step-by-step checks and evidence gathering by examining pods, logs, events, and cluster state, which concludes by reporting findings with actionable recommendations.