openshift-cluster-health-check

Assess OpenShift cluster health with a 17-phase diagnostic workflow.

2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/tomazb/agent-skills --skill openshift-cluster-health-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openshift-cluster-health-check
Source: https://github.com/tomazb/agent-skills/tree/main/openshift-cluster-health-check
Command: npx skills add https://github.com/tomazb/agent-skills --skill openshift-cluster-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive diagnostic workflow to assess the health of an OpenShift cluster. It identifies potential issues across various platform types and classifies them with severity levels.

Core Features & Use Cases

  • 17-phase diagnostic workflow: Covers platform detection, cluster operators, nodes, MCPs, etcd, auth, ingress, DNS, networking, storage, monitoring, image registry, console, certificates, platform-specific, pod health, and cluster-wide events.
  • Platform-aware: Supports bare metal, virtualized, cloud, and SNO environments.
  • Health classification: Provides clear categorization of findings as Healthy, Warning, or Critical.
  • Pod classification: Differentiates between quota-blocked and platform-blocked pending pods and identifies CrashLoopBackOff cases.
  • Safety-first: Default read-only operations to ensure no accidental changes to the cluster.

Quick Start

Use the 'oc cluster-health-check' command to initiate the health check on the OpenShift cluster.

Frequently Asked Questions about openshift-cluster-health-check

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

FAQPage Schema
How do I run an OpenShift cluster health check across different platform types?

Assess OpenShift cluster health using a 17-phase diagnostic workflow that covers bare metal, virtualized, cloud, and SNO environments. Run the health check command to evaluate cluster operators, nodes, etcd, and networking components.

What does an OpenShift cluster diagnostic workflow examine?

An OpenShift cluster diagnostic workflow examines platform detection, cluster operators, nodes, MCPs, etcd, auth, ingress, DNS, networking, storage, monitoring, image registry, console, certificates, and cluster-wide events to identify potential issues.

Can I perform OpenShift cluster diagnostics without modifying the cluster?

Yes, you can perform OpenShift cluster diagnostics safely. The health check workflow uses default read-only operations to ensure no accidental changes occur to the cluster while identifying potential issues across components.

How are pending pods and CrashLoopBackOff cases classified in OpenShift health checks?

OpenShift health checks classify pending pods by differentiating between quota-blocked and platform-blocked instances. The diagnostic workflow also identifies CrashLoopBackOff cases and categorizes all findings as Healthy, Warning, or Critical.

Does the OpenShift health check support Single Node OpenShift (SNO) environments?

Yes, the OpenShift health check supports Single Node OpenShift (SNO) environments. The platform-aware diagnostic workflow covers bare metal, virtualized, cloud, and SNO installations to provide severity classification for findings.