Must-Gather Analyzer

Analyze OpenShift must-gather YAML data to diagnose cluster health issues.

112|305|Updated Oct 10, 2025

Search Tags:#troubleshooting #kubernetes #must-gather #diagnostics #openshift #cluster-health

Ready to run

npx skills add https://github.com/openshift-eng/ai-helpers --skill must-gather-analyzer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Must-Gather Analyzer
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/must-gather/skills/must-gather-analyzer
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill must-gather-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill transforms complex OpenShift must-gather diagnostic data into actionable insights, helping you quickly identify and resolve cluster problems.

Core Features & Use Cases

Comprehensive Analysis: Analyze cluster operators, pods, nodes, network, storage, and etcd health.
Root Cause Analysis: Follow dependency chains from degraded operators to failing pods to problematic nodes.
Use Case: When your cluster shows degraded operators, use this Skill to identify which specific pods are failing, which nodes they're running on, and what specific conditions are causing the issues.

Quick Start

Use the Must-Gather Analyzer skill to check the health of cluster operators in the must-gather data located at './must-gather.local.123456789'.

Frequently Asked Questions about Must-Gather Analyzer

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

FAQPage Schema

How do I diagnose OpenShift cluster issues from must-gather data?▼

Must-gather exports contain cluster diagnostics you can analyze to identify root causes. The Must-Gather Analyzer parses ClusterVersion, ClusterOperators, Pods, Nodes, Network, etcd, and Storage resources to surface health problems, dependency chains from degraded operators to failing pods, and actionable remediation steps in a structured format.

Can I use must-gather analysis to troubleshoot degraded cluster operators?▼

Yes. The Analyzer traces operator degradation to specific failing pods and problematic nodes. It follows dependency chains to show which pods are affected, their host nodes, and the conditions causing the issues, helping you resolve operator problems systematically.

What Kubernetes and OpenShift resources does the analyzer examine?▼

The Analyzer inspects ClusterVersion, ClusterOperators, Pods, Nodes, Network, etcd, and Storage resources across cluster and namespace scopes. It processes YAML outputs and generates summaries, tables, and issue breakdowns similar to `oc` command output for rapid diagnosis.

Do I need to export the entire cluster or can I analyze specific namespaces?▼

The Analyzer works with both full root must-gather exports and per-namespace subsets, giving you flexibility to diagnose cluster-wide health or isolate problems to individual namespaces depending on your troubleshooting scope.

What format does the analyzer output for cluster diagnostics?▼

The Analyzer outputs concise summaries, structured tables, and issue breakdowns formatted like standard `oc` command output, making results immediately actionable and familiar to OpenShift operators and administrators.

How do I start analyzing must-gather data for cluster health?▼

Point the Analyzer to your must-gather export directory (e.g., `./must-gather.local.123456789`). It automatically parses the contained YAML resources and produces a comprehensive health report identifying operators, pods, nodes, network, storage, and etcd problems with root-cause insights.