k8s-nfs-mount-troubleshooting

Diagnose Kubernetes NFS mount failures causing ContainerCreating pod states.

5|Updated Feb 7, 2021
One-click install
npx skills add https://github.com/ViktorBarzin/infra --skill k8s-nfs-mount-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-nfs-mount-troubleshooting
Source: https://github.com/ViktorBarzin/infra/tree/main/.claude/skills/k8s-nfs-mount-troubleshooting
Command: npx skills add https://github.com/ViktorBarzin/infra --skill k8s-nfs-mount-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides DevOps through diagnosing and fixing Kubernetes NFS mount failures on pods, reducing MTTR and outages.

Core Features & Use Cases

  • Root-cause identification: quickly determine if the issue is due to a missing NFS export, incorrect export path, or server permissions.
  • Step-by-step remediation: provides commands and checks to verify the NFS server export, create missing directories, and re-deploy pods.
  • Use Case: when a pod is stuck in ContainerCreating with MountVolume errors, follow this guide to restore NFS mounts.

Quick Start

Follow these steps to verify the NFS path on the cluster and server and recreate missing export directories.

Frequently Asked Questions about k8s-nfs-mount-troubleshooting

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

FAQPage Schema
Why is my Kubernetes pod stuck in ContainerCreating with a MountVolume error?

Kubernetes pods get stuck in ContainerCreating with MountVolume errors when the NFS server denies access, the export path is missing, or the NFS export is misconfigured. You must verify the NFS export and path on both the cluster and the NFS server to diagnose the failure.

How do I fix access denied errors when mounting an NFS volume in Kubernetes?

To fix NFS access denied errors in Kubernetes, validate the NFS path existence and verify the export configuration on the NFS server. After correcting the server permissions or export paths, re-deploy the affected pods to restore the mounts successfully.

What causes protocol not supported errors during Kubernetes NFS volume setup?

Protocol not supported errors during Kubernetes NFS volume setup usually indicate a mismatch between the cluster mount attempt and the NFS server export configuration. Verifying the NFS export settings on the server side is required to resolve this mount failure.

How do I verify a missing NFS export path for a Kubernetes mount failure?

To verify a missing NFS export path for a Kubernetes mount, run checks against the NFS server to confirm directory existence and export configuration. If the directory is missing, create it on the server and restart the pod to sequence the mount recovery.

What steps are needed to recover a failed NFS mount in a Kubernetes cluster?

Recovering a failed Kubernetes NFS mount requires validating NFS path existence, confirming export configuration, and following pod restart sequencing. These steps identify if the root cause is a missing export, incorrect path, or server permission issue.