kube-medic

You can run a full cluster health triage by asking the tool to analyze your Kubernetes environment with optional context and namespace settings. It orchestrates read-only queries across nodes, pods, and events to surface critical problems and provide AI-assisted diagnostics.

Yes, multi-cluster Kubernetes diagnostics are supported by operating across different contexts and namespaces. This allows you to manage large environments and perform detailed pod autopsies, including container statuses, current and previous logs, and image mismatches.

Yes, kubectl and jq are required dependencies for performing read-only Kubernetes diagnostics. They gather cluster data, execute safe reads, and process JSON output for downstream AI reasoning during incident response and cluster triage.

Analyzing node-resource pressure and deployment rollout status requires querying replicasets, rollout history, and node utilization. An AI-assisted triage tool correlates this data to provide deployment insights and identify resource constraints across the Kubernetes cluster.

No, this Kubernetes diagnostics tool performs strictly read-only operations during incident response. It gathers data on nodes, pods, and events safely without modifying cluster resources, ensuring secure triage and analysis.