hypershift:quotas

Check AWS service quotas and usage before HyperShift cluster deployments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps prevent deployment failures and ensures sufficient cloud resources by checking AWS service quotas and current usage before creating HyperShift clusters.

Core Features & Use Cases

  • Capacity Planning: Assesses availability of critical AWS resources like VPCs, NAT Gateways, Elastic IPs, Security Groups, NLBs, IAM Roles, and Route53 Hosted Zones.
  • Automated Checks: Provides a quick command-line check for all relevant quotas and usage.
  • Quota Increase Requests: Facilitates requesting quota increases for under-provisioned resources.
  • Use Case: Before launching a new HyperShift cluster in a CI/CD pipeline, this Skill automatically verifies that enough VPCs, NAT Gateways, and Elastic IPs are available to avoid deployment errors.

Quick Start

Run the command ./.github/scripts/hypershift/check-quotas.sh to check all AWS quotas and usage for HyperShift.

Frequently Asked Questions about hypershift:quotas

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

FAQPage Schema
How do I check AWS quotas for HyperShift cluster deployments?

To check AWS quotas for HyperShift, run the provided check-quotas.sh script to compare current resource utilization against service limits for VPCs, NAT gateways, Elastic IPs, and EC2 instances. This prevents deployment failures caused by insufficient cloud capacity.

What AWS resources are validated before creating a HyperShift cluster?

Validating AWS resources for HyperShift involves checking capacity limits for VPCs, NAT gateways, Elastic IPs, EC2 instances, security groups, load balancers, S3 buckets, IAM roles, and Route53 zones. Identifying these bottlenecks early ensures smooth cluster provisioning.

Can I automate AWS quota increase requests for HyperShift capacity planning?

Yes, you can automate AWS quota increase requests for HyperShift capacity planning. The Skill identifies under-provisioned resources during its utilization checks and facilitates automated requests for quota increases, while also providing manual verification steps via AWS CLI commands.

Why does my HyperShift deployment fail with cloud capacity errors?

HyperShift deployments fail with cloud capacity errors when AWS service quotas for critical resources like VPCs, NAT gateways, or Elastic IPs are exhausted. Running a pre-deployment quota check identifies these specific bottlenecks to prevent provisioning failures.

Does this AWS quota check work in a CI/CD pipeline?

Yes, this AWS quota check works in a CI/CD pipeline. You can run the command-line script to automatically verify that enough VPCs, NAT gateways, and Elastic IPs are available before launching a new HyperShift cluster, avoiding deployment errors.

What is the best way to verify AWS service limits for HyperShift?

The best way to verify AWS service limits for HyperShift is running the dedicated check-quotas.sh script. It provides a quick command-line assessment of all relevant quotas and current usage, ensuring sufficient cloud resources are available before deployment.