oke-troubleshooter

Name: oke-troubleshooter
Availability: InStock
Author: chiphwang1

Diagnose OKE incidents by correlating Kubernetes symptoms with OCI infrastructure signals.

Updated Mar 7, 2026

Search Tags:#troubleshooting #kubernetes #diagnostics #cloud native #oci #oke

Ready to run

npx skills add https://github.com/chiphwang1/oke-agent-plugin-improvement --skill oke-troubleshooter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oke-troubleshooter
Source: https://github.com/chiphwang1/oke-agent-plugin-improvement/tree/main/skills/oke-troubleshooter
Command: npx skills add https://github.com/chiphwang1/oke-agent-plugin-improvement --skill oke-troubleshooter

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you diagnose and troubleshoot issues within your Oracle Kubernetes Engine (OKE) clusters by correlating Kubernetes symptoms with OCI infrastructure signals.

Core Features & Use Cases

End-to-end Diagnosis: Identifies root causes for common OKE problems like pending pods, network failures, or performance degradation.
Evidence-driven Analysis: Collects relevant logs and metrics from both Kubernetes and OCI to pinpoint issues.
Use Case: If your application pods are stuck in a "Pending" state, this Skill will investigate scheduling conflicts, resource availability, and node health to provide a clear explanation and remediation steps.

Quick Start

Use the oke-troubleshooter skill to diagnose why pods are stuck Pending in the prod namespace.

Frequently Asked Questions about oke-troubleshooter

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

FAQPage Schema

How do I troubleshoot pending pods in an OKE cluster?▼

To troubleshoot pending pods in OKE, you must investigate scheduling conflicts, resource availability, and node health. Correlating Kubernetes symptoms with OCI infrastructure signals identifies the root cause and guides remediation.

What is the best way to diagnose Kubernetes networking failures on Oracle Cloud Infrastructure?▼

Diagnosing Kubernetes networking failures on OCI requires an end-to-end approach. Collecting evidence from logs and metrics across both Kubernetes and OCI layers pinpoints the exact infrastructure conflict.

How does root-cause analysis work for cloud native cluster performance degradation?▼

Root-cause analysis for cluster performance degradation works by guiding you through evidence collection and hypothesis ranking. It correlates application symptoms with underlying OCI infrastructure signals to isolate issues.

Can I use this diagnostics approach for OKE node health and runtime issues?▼

Yes, you can use this diagnostics approach for OKE node health and runtime issues. The method supports troubleshooting pod scheduling, runtime behaviors, and node health by analyzing correlated OCI signals.

Why are my application pods stuck in a Pending state on Oracle Kubernetes Engine?▼

Application pods get stuck in a Pending state on Oracle Kubernetes Engine due to scheduling conflicts or insufficient resource availability. Diagnosing the issue requires checking node health and OCI infrastructure metrics.