pvc-debug

Diagnose PersistentVolumeClaim failures in Kubernetes using kubectl.

225|28|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/scitix/siclaw --skill pvc-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pvc-debug
Source: https://github.com/scitix/siclaw/tree/main/skills/core/pvc-debug
Command: npx skills add https://github.com/scitix/siclaw --skill pvc-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and identify the root cause of PersistentVolumeClaim (PVC) failures in Kubernetes, such as PVCs stuck in Pending state, storage provisioning issues, or binding problems.

Core Features & Use Cases

  • Diagnose PVC Status: Checks PVC, PV, and StorageClass configurations.
  • Identify Provisioning Errors: Analyzes events for dynamic provisioning failures.
  • Troubleshoot Binding Issues: Detects mismatches in capacity, access modes, or StorageClasses for static provisioning.
  • Use Case: When a new application deployment fails because its PVC is stuck in Pending, this Skill can quickly pinpoint whether the issue lies with the StorageClass, available PersistentVolumes, or dynamic provisioner errors.

Quick Start

Use the pvc-debug skill to diagnose a pending PVC named 'my-data-pvc' in the 'production' namespace.

Frequently Asked Questions about pvc-debug

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

FAQPage Schema
Why is my Kubernetes PersistentVolumeClaim stuck in Pending state?

A PersistentVolumeClaim stuck in Pending state usually indicates storage class not found errors, dynamic provisioning failures, or static binding mismatches. Analyzing PVC, PV, StorageClass, and provisioner events determines the exact root cause.

How do I debug Kubernetes PVC storage class not found errors?

To debug Kubernetes PVC storage class not found errors, diagnose the PersistentVolumeClaim configurations and check dynamic provisioner events. This identifies whether the StorageClass is missing, misconfigured, or failing to provision volumes.

How do I troubleshoot PersistentVolume binding issues in Kubernetes?

Troubleshoot PersistentVolume binding issues by checking for mismatches in capacity, access modes, or StorageClasses. Analyzing the PVC and PV configurations reveals why static provisioning fails to bind the requested volume.

Can I use kubectl to diagnose PVC provisioning failures?

Yes, you can use kubectl to diagnose PVC provisioning failures. This Skill requires kubectl for cluster interaction to analyze PVC, PV, StorageClass, and provisioner events to determine why storage remains unavailable.

What causes dynamic volume provisioning errors in Kubernetes?

Dynamic volume provisioning errors in Kubernetes are caused by StorageClass misconfigurations or provisioner failures. Analyzing cluster events determines if the dynamic provisioner is failing to create the requested PersistentVolume.