kubernetes-sigs/nfs-subdir-external-provisioner

Dynamic sub-dir volume provisioner on a remote NFS server.

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on March 26th, 2020
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 834
Total Stargazers: 3,049 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.1 days
Mean response time: 74.6 days
90th percentile: 145.0 days
Tracked items: 30

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 7, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 234 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • lifecycle/rotten (35)
  • lifecycle/stale (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

NFS Subdir External Provisioner is a Kubernetes storage provisioner that dynamically provisions Persistent Volumes from an existing NFS server.

The tool solves the problem of automating volume provisioning for Kubernetes clusters that already have an NFS server available. Rather than requiring manual creation of Persistent Volumes, it watches for Persistent Volume Claims and automatically creates subdirectories on the remote NFS server to back them, naming each volume as a combination of namespace, claim name, and volume name. This approach leverages existing NFS infrastructure without requiring changes to the server itself.

Teams should adopt this provisioner if they have an operational NFS server and want to enable dynamic storage provisioning in their Kubernetes clusters without managing individual volume creation. It suits environments where NFS is the preferred or available storage backend. The tool can be deployed via Helm or Kustomize, with straightforward configuration requiring only the NFS server's hostname and exported share path. The README explicitly notes this is a migration from an earlier incubator project, with the container image now hosted at the official Kubernetes registry.

The project acknowledges that automated end-to-end testing remains a pending development area and explicitly invites contributions in this space. Development activity centers on the core provisioning functionality, with the team maintaining compatibility with earlier deployment approaches while updating the underlying container infrastructure.