openshift:debug

Diagnose OpenShift cluster operator, authentication, route, and build failures.

292|103|Updated Mar 27, 2025
One-click install
npx skills add https://github.com/kagenti/kagenti --skill openshift-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openshift:debug
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/openshift%3Adebug
Command: npx skills add https://github.com/kagenti/kagenti --skill openshift-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oc, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve issues related to OpenShift clusters, operators, and platform configurations, streamlining troubleshooting for complex Kubernetes environments.

Core Features & Use Cases

  • Cluster Health Checks: Quickly assess the status of cluster operators and identify degraded components.
  • Operator Debugging: Inspect operator logs, install plans, and subscriptions to pinpoint failures.
  • Authentication & Route Troubleshooting: Diagnose problems with OAuth, routes, and ingress controllers.
  • Build Issue Resolution: Analyze build failures and their logs.
  • Use Case: When an OpenShift operator is not functioning correctly, use this skill to gather logs and configuration details for rapid diagnosis.

Quick Start

Use the openshift:debug skill to check the status of all cluster operators and list any that are degraded.

Frequently Asked Questions about openshift:debug

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

FAQPage Schema
How do I troubleshoot a degraded OpenShift cluster operator?

Troubleshooting a degraded OpenShift cluster operator involves executing context-safe commands to check cluster health, inspect operator status, and gather configuration details for rapid diagnosis.

What is the best way to diagnose OpenShift authentication and route failures?

Diagnosing OpenShift authentication and route failures involves gathering specific resource configurations to pinpoint problems with OAuth, routes, and ingress controllers.

How do I analyze OpenShift build failures and their logs?

Analyzing OpenShift build failures involves running diagnostic commands to retrieve and parse build logs, helping you identify the root cause of the failure.

Do I need the oc CLI and jq to debug Kubernetes operators on OpenShift?

Debugging Kubernetes operators on OpenShift requires the `oc` CLI for command execution and `jq` for advanced parsing of the diagnostic output.

Can I inspect OpenShift install plans and subscriptions to pinpoint operator failures?

You can inspect OpenShift install plans and subscriptions to pinpoint operator failures by gathering operator logs and configuration details using context-safe commands.