rancher-resource-troubleshooting

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.

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.

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.

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.

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.