hypershift:debug

Debug AWS resources blocking HyperShift cluster deletion.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps diagnose and resolve issues with AWS resources related to HyperShift clusters, specifically targeting stuck resources, orphaned infrastructure, and deletion blockers.

Core Features & Use Cases

  • Resource Identification: Pinpoints AWS resources that are preventing cluster deletion or are no longer associated with an active cluster.
  • Log Analysis: Provides commands to inspect HyperShift operator logs for errors and permission issues.
  • Cleanup Guidance: Offers a structured order for manual resource cleanup and commands to force finalizer removal.
  • Use Case: When a HyperShift cluster deletion is stuck in a pending state, this Skill can be used to identify which AWS resources (like VPCs, Security Groups, or Load Balancers) are holding up the process and provide steps to resolve it.

Quick Start

Use the hypershift:debug skill to find stuck AWS resources for the cluster named 'my-cluster'.

Frequently Asked Questions about hypershift:debug

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

FAQPage Schema
Why is my HyperShift cluster deletion stuck in a pending state?

HyperShift cluster deletion gets stuck when orphaned AWS resources like VPCs or load balancers block finalizers. This Skill identifies those specific deletion blockers and provides commands to force finalizer removal and clean up infrastructure.

How do I debug orphaned AWS resources for a HyperShift cluster?

Debug orphaned AWS resources by checking EC2 instances, VPCs, subnets, security groups, and S3 buckets using AWS CLI commands. This Skill scopes these resources to pinpoint infrastructure no longer associated with an active cluster.

Do I need AWS CLI and oc configured to troubleshoot HyperShift cluster issues?

Yes, troubleshooting HyperShift cluster issues requires AWS CLI and oc or kubectl configured with appropriate credentials and context. This setup allows the Skill to inspect HostedCluster status and operator logs effectively.

How do I check HyperShift operator logs for permission errors?

Check HyperShift operator logs for permission errors by running specific oc or kubectl commands provided by this Skill. It analyzes log outputs to identify errors and permission issues preventing proper cluster resource management.

What is the best way to clean up stuck AWS infrastructure preventing HostedCluster deletion?

The best way to clean up stuck AWS infrastructure is following a structured manual resource cleanup order. This Skill offers specific commands to force finalizer removal and resolve deletion blockers for HostedCluster resources.

Can I identify Route53 zones and IAM roles blocking my HyperShift cluster deletion?

Yes, you can identify Route53 zones and IAM roles blocking HyperShift cluster deletion. This Skill scopes these specific AWS resources to find orphaned infrastructure and provides steps to resolve pending deletion states.