infra-kubernetes-storage-review

Reviews Kubernetes persistent storage configuration for PVC binding, performance, and lifecycle issues.

14|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/ivanshamaev/de-agent-skills --skill infra-kubernetes-storage-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra-kubernetes-storage-review
Source: https://github.com/ivanshamaev/de-agent-skills/tree/main/group_skills/infra_dataops_group_skills/infra_kubernetes_storage_review
Command: npx skills add https://github.com/ivanshamaev/de-agent-skills --skill infra-kubernetes-storage-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review and fix Kubernetes storage configuration so stateful workloads don’t get stuck, underperform, or lose data through incorrect StorageClass, access modes, lifecycle settings, or orphaned PVs.

Core Features & Use Cases

  • PVC lifecycle troubleshooting: Diagnose Pending/Unbound/Lost/Released states and identify why a claim cannot bind.
  • StorageClass selection & governance: Choose appropriate block/filesystem storage, provisioning mode (dynamic vs static), binding mode, reclaim policy, and expansion capability.
  • Stateful volume planning: Validate StatefulSet volumeClaimTemplates, access modes (RWO/ROX/RWX/RWOP), and safe volume resize and snapshot/restore workflows.
  • Cost and hygiene audits: Detect orphaned or Released PVs that still consume resources and highlight large, expensive PVCs.

Quick Start

Ask the AI to review your StorageClass and PVC status outputs for Pending claims and recommend the minimal set of changes needed to bind correctly and safely for your workload.

Frequently Asked Questions about infra-kubernetes-storage-review

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

FAQPage Schema
Why is my Kubernetes PVC stuck in Pending state and how do I fix it?

A Pending PVC binding issue usually means the requested StorageClass is missing, access modes mismatch, or insufficient capacity. Inspecting kubectl PVC/PV state diagnostics helps identify the exact binding failure and recommend minimal configuration changes to resolve it safely.

How do I choose the right StorageClass parameters for stateful workloads across cloud providers?

Choosing the right StorageClass requires evaluating block vs filesystem provisioning, dynamic vs static binding, reclaimPolicy, and allowVolumeExpansion. Validating these parameters against your provider-specific CSI driver ensures safe stateful data lifecycle management and performance.

Can I expand a Kubernetes PVC and restore it from a volume snapshot safely?

PVC expansion and snapshot restore are safe when the StorageClass has allowVolumeExpansion enabled and proper CSI snapshot practices are followed. Validating StatefulSet volumeClaimTemplates and access modes like RWO or RWX ensures data reliability during these operations.

What is the best way to clean up orphaned PersistentVolumes that still consume resources?

Cleaning up orphaned PVs involves inspecting Released or Lost PVC states and validating reclaimPolicy settings. A storage hygiene audit detects expensive PVCs and orphaned volumes, recommending safe removal to stop unnecessary resource consumption and cost overhead.

How do I validate StatefulSet volumeClaimTemplates for correct access modes?

Validating StatefulSet volumeClaimTemplates requires checking access modes like RWO, ROX, RWX, and RWOP against the chosen StorageClass. Ensuring proper alignment prevents performance mismatches and unsafe lifecycle settings for stateful data workloads.

Does this Kubernetes storage review work with provider-specific CSI drivers?

Yes, the storage review applies provider-specific CSI and snapshot/backup practices to validate StorageClass configuration. It requires kubectl-driven inspection of PV state to resolve binding issues and performance mismatches across different cloud providers.