ksail cluster diagnose

Surface failing Kubernetes resources for the current cluster.

This command inspects the live cluster via the Kubernetes API and reports
any pods that are not running successfully and any nodes that are not Ready.
It is distribution-agnostic and works with Vanilla, K3s, Talos, and
VCluster.

The output is intentionally compact so it can be consumed directly by users
or by the KSail AI chat assistant (ksail chat) and MCP server, which expose
this command as part of the cluster_read tool. When used from the AI
assistant the output is fed back as context so Copilot can explain the root
cause and suggest remediation.

The cluster is resolved in the following priority order:
  1. From --name flag
  2. From ksail.yaml config file (if present)
  3. From current kubeconfig context

Exit code 0 is returned even when pod or node failures are reported.
A non-zero exit code indicates the Kubernetes API could not be queried
(e.g., the cluster is unreachable or the credentials lack sufficient
permissions).

Usage:
  ksail cluster diagnose [flags]

Flags:
  -n, --name string         Name of the cluster to target
  -p, --provider Provider   Provider to use ([Docker Hetzner Omni AWS])

Global Flags:
      --benchmark       Show per-activity benchmark output
      --config string   Path to config file (default: ksail.yaml found via directory traversal)