Diagnose Kubernetes ResourceQuota and LimitRange admission rejections preventing pod creation.
npx skills add https://github.com/scitix/siclaw --skill quota-debug
Please help me install this Agent Skill. Skill: quota-debug Source: https://github.com/scitix/siclaw/tree/main/skills/core/quota-debug Command: npx skills add https://github.com/scitix/siclaw --skill quota-debug
This Skill helps diagnose and resolve issues where pods cannot be created in Kubernetes due to exceeding resource quotas or violating limit range constraints.
FailedCreate with messages like "exceeded quota" or "forbidden: LimitRange", this skill guides you through checking namespace quotas, current usage, and LimitRange configurations to find the exact cause.Use the quota-debug skill to diagnose why pods are failing to be created in the 'default' namespace.
High-intent search queries and answers about installing and using this skill.
Kubernetes pod creation fails with exceeded quota errors when a namespace's ResourceQuota for CPU, memory, pods, or storage is fully exhausted. Diagnosing the issue requires analyzing current resource usage against namespace quotas to identify the exhausted dimension.
Debug Kubernetes LimitRange violations by pinpointing specific constraint breaches like minimum or maximum resource requirements, ratio constraints, or missing resource specifications in pod manifests. Analyze ReplicaSet events to find the exact Forbidden LimitRange rejection cause.
FailedCreate errors in a Kubernetes ReplicaSet occur when admission control rejects pod creation due to ResourceQuota exhaustion or LimitRange violations. Analyzing namespace quotas, current usage, and LimitRange constraints identifies the specific root cause.
Check if a Kubernetes namespace ResourceQuota is exhausted by validating current resource usage against configured quota dimensions for CPU, memory, pods, and storage. This comparison reveals which specific resource limit is preventing new pod creation.
Missing resource specifications cause Kubernetes pod creation failures when LimitRange constraints require explicit resource requests or limits. The admission controller rejects pods lacking these specifications to enforce namespace resource governance policies.
This Skill diagnoses Kubernetes native ResourceQuota and LimitRange admission rejections specifically. It validates quota dimensions like CPU and memory, and checks LimitRange specifics including minimums, maximums, ratios, and defaults.
foxj77Provision multi-tenant Kubernetes namespaces with RBAC, quotas, and network policies.
snoodleboot-ioOptimize Kubernetes resource requests, limits, quotas, and priority classes.
adaptive-enforcement-labEnforce Kubernetes CPU, memory, and storage limits with OPA policies.
Lobbi-DocsAutomate Kubernetes deployment, management, and troubleshooting workflows.