rancher-resource-troubleshooting

Automates Kubernetes pod and system fault diagnosis via Juniper-supplied tools and Runner APIs.

1|1|Updated Feb 17, 2026

Search Tags:#logs #kubernetes #events #multi-cluster #rancher #pod-diagnosis #deployment-tracker

Ready to run

npx skills add https://github.com/futuretea/rancher-assistant --skill rancher-resource-troubleshooting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rancher-resource-troubleshooting
Source: https://github.com/futuretea/rancher-assistant/tree/main/skills/resource-troubleshooting
Command: npx skills add https://github.com/futuretea/rancher-assistant --skill rancher-resource-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly diagnose Kubernetes Pod and resource issues, surfacing logs, events, and status to identify root causes and reduce MTTR.

Core Features & Use Cases

Direct data access: retrieve Pod logs, events, and resource descriptions to rapidly understand state.
Targeted delegation: hand deep diagnostics to rancher-pod-diagnostician and rancher-deployment-tracker for complex scenarios.
Parallel analysis: diagnose across multiple Pods or Deployments and consolidate results for multi-cluster environments.

Quick Start

Diagnose a failing Pod by providing the cluster, namespace, and pod name to get logs, events, and status.

Frequently Asked Questions about rancher-resource-troubleshooting

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

FAQPage Schema

How do I diagnose Kubernetes pod crashes and failed deployments?▼

Diagnose Kubernetes pod crashes by retrieving pod logs, events, and resource descriptions to surface state and identify root causes quickly. This automated diagnosis reduces mean time to recovery by consolidating status information for failed deployments.

Can I troubleshoot resource outages across multiple Kubernetes clusters simultaneously?▼

Yes, you can troubleshoot resource outages across multiple Kubernetes clusters simultaneously using parallel execution. It diagnoses multiple pods or deployments concurrently and consolidates results for multi-cluster environments.

What is the best way to get Kubernetes logs and events for troubleshooting?▼

The best way to get Kubernetes logs and events is using direct data retrieval functions. Access kubernetes_logs, kubernetes_events, and kubernetes_describe to rapidly understand resource state and surface root causes during troubleshooting.

When do I need deep diagnostics for Kubernetes pod issues?▼

You need deep diagnostics for Kubernetes pod issues when basic logs and events are insufficient. Complex scenarios are delegated to specialized diagnostician and deployment tracker tools for deeper analysis and tracking.

Does this approach work for diagnosing deployment failures in a single cluster?▼

Yes, this approach works for diagnosing deployment failures in a single cluster. It supports direct data retrieval and targeted delegation to analyze failed deployments across both single and multi-cluster Kubernetes environments.