check-ocp-health

Diagnose OpenShift cluster health issues and provide kubectl remediation commands.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/yaacov/forklift-skills --skill check-ocp-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-ocp-health
Source: https://github.com/yaacov/forklift-skills/tree/main/skills/check-ocp-health
Command: npx skills add https://github.com/yaacov/forklift-skills --skill check-ocp-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

General OpenShift (OCP) cluster health check. Use when the cluster is unhealthy, nodes are NotReady, operators are degraded, pods are crashing, etcd is slow, networking issues occur, or a general cluster diagnosis is needed.

Core Features & Use Cases

  • Node & Operator Triage: Assess node readiness, capacity, and operator health to identify degraded components.
  • Workload & API Health: Review pod states, API responsiveness, and critical cluster resources (etcd, MCP, certificates).
  • Diagnostics & Remediation Guidance: Provide structured steps to diagnose root causes and recommended remediations.

Quick Start

Run the OpenShift cluster health triage to identify issues and remediation steps.

Frequently Asked Questions about check-ocp-health

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

FAQPage Schema
How do I troubleshoot OpenShift nodes that are stuck in a NotReady state?

To troubleshoot OpenShift NotReady nodes, run the cluster health triage to assess node readiness and capacity. This diagnostic identifies degraded components and provides step-by-step kubectl commands to check node conditions and operators to guide triage.

What kubectl commands diagnose degraded OpenShift cluster operators?

Diagnosing degraded OpenShift cluster operators involves running structured kubectl commands provided by the health check. It assesses operator health, reviews cluster version status, and outputs recommended remediation steps to restore degraded components.

Can I check etcd latency and API server responsiveness in an OCP cluster?

Yes, you can check etcd latency and API server responsiveness in an OCP cluster. The health check reviews critical cluster resources including etcd, API server responsiveness, and certificates to identify performance bottlenecks and networking issues.

How do I find the root cause of crash-looping pods in OpenShift?

Finding the root cause of crash-looping pods in OpenShift requires reviewing pod states and workload health. The health check provides structured kubectl commands to inspect pods, diagnose root causes, and offers recommended remediations to resolve the crashes.

Does OpenShift health checking cover MachineConfigPool and quota diagnostics?

Yes, OpenShift health checking covers MachineConfigPool (MCP) and quota diagnostics. The triage process includes specific kubectl commands to inspect MCP status, cluster version, and quotas to ensure overall cluster configuration and resource limits are healthy.