Debug Cluster

Troubleshooting a stuck deletion uses systematic workflows to identify whether the issue originates in NodePools, HostedControlPlane resources, or namespace cleanup. The Skill applies provider-agnostic diagnostic steps with kubectl and operator logs across HostedCluster, HostedControlPlane, NodePool, and CAPI resources to isolate the root cause.

Debugging workflows address deletion issues, stuck resources and finalizers, control plane problems, and NodePool lifecycle events. The Skill enforces standardized command sequences and coordinated checks across cluster resources with hooks to provider-specific subskills for comprehensive problem diagnosis.

Yes. The Skill provides provider-agnostic debugging approaches that work across all cloud platforms. It applies the same structured troubleshooting methodologies regardless of whether your hosted cluster runs on AWS, Azure, GCP, or other providers.

Investigating control plane issues uses standardized diagnostic sequences including kubectl commands and operator log analysis. The Skill systematically checks HostedControlPlane and HostedCluster resources to identify whether the problem stems from resource constraints, configuration drift, or lifecycle events.

Checking NodePool resources involves examining lifecycle events, finalizers, and resource deletion status through coordinated checks. The Skill provides structured steps to determine whether NodePool problems are blocking cluster operations or preventing successful deletion.

Yes. HyperShift cluster debugging requires familiarity with Kubernetes concepts like resources, namespaces, and kubectl commands. The Skill builds on this foundation by automating workflows and providing expert troubleshooting methodologies for hosted-cluster-specific issues.