Storage Operations

Diagnoses Rook-Ceph and local-path-provisioner storage issues in Kubernetes clusters.

9|3|Updated Apr 16, 2024
One-click install
npx skills add https://github.com/keiretsu-labs/kubernetes-manifests --skill storage-operations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Storage Operations
Source: https://github.com/keiretsu-labs/kubernetes-manifests/tree/main/openclaw/workspaces/main/skills/storage-ops
Command: npx skills add https://github.com/keiretsu-labs/kubernetes-manifests --skill storage-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and troubleshoot storage-related problems across Kubernetes clusters, ensuring data availability and performance.

Core Features & Use Cases

  • Rook-Ceph Diagnostics: Provides detailed health checks for Rook-Ceph deployments in Ottawa and Robbinsdale clusters, including cluster status, OSD health, and pool usage.
  • Local-Path Troubleshooting: Assists with issues related to the local-path-provisioner on the St. Petersburg cluster.
  • PVC Status Monitoring: Helps identify and resolve Persistent Volume Claim (PVC) issues like Pending or Lost states, and volume attachment errors.
  • Use Case: When users report that their applications cannot start due to storage being unavailable or PVCs stuck in Pending, this Skill can be used to quickly pinpoint whether the issue is with Ceph health, pool capacity, or a misconfiguration.

Quick Start

Run a storage health check for the talos-ottawa cluster.

Frequently Asked Questions about Storage Operations

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

FAQPage Schema
How do I troubleshoot a PVC stuck in Pending state in Kubernetes?

To troubleshoot a Pending PVC, you need to check storage class availability, cluster capacity, and volume attachment errors. This Skill diagnoses binding failures by inspecting Rook-Ceph pool capacity and local-path-provisioner status to pinpoint the root cause.

Why is my Rook-Ceph cluster unhealthy and how can I check OSD status?

A Rook-Ceph cluster becomes unhealthy when OSDs fail or placement groups degrade. This Skill checks Ceph cluster health by inspecting OSD status, placement group states, and pool capacity across specified Kubernetes cluster contexts using kubectl.

Can I use this to diagnose local-path-provisioner volume attachment errors?

Yes, you can diagnose local-path-provisioner issues with this Skill. It helps identify and resolve volume attachment errors and Persistent Volume Claim problems for clusters relying on local-path storage provisioning.

What's the best way to run a Rook-Ceph storage health check on a specific cluster?

The best way to run a Rook-Ceph health check is by executing diagnostic commands through kubectl against the specified cluster context. This Skill automates checking cluster status, OSD health, and pool usage for targeted clusters.

Do I need kubectl access to diagnose Kubernetes storage issues?

Yes, you need kubectl access to specified cluster contexts to execute diagnostic commands. This Skill requires direct cluster access to retrieve Ceph cluster health, OSD status, placement group states, and PVC binding information.

What Kubernetes storage issues does this Skill help resolve?

This Skill resolves Kubernetes storage issues including unavailable storage preventing application startup, PVCs stuck in Pending or Lost states, Rook-Ceph health degradation, pool capacity exhaustion, and volume attachment errors.