openebs/lvm-localpv

Dynamically provision Stateful Persistent Node-Local Volumes & Filesystems for Kubernetes that is integrated with a backend LVM2 data storage stack.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

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

openebs/lvm-localpv has 350+ stars and 100+ forks on GitHub, is written in Go, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 59 minutes ago
Added to GitGenius on October 15th, 2026
Created on December 23rd, 2020
Open Issues & Pull Requests: 29 (+0)
GitHub issues: Enabled
Number of forks: 129
Total Stargazers: 357 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.3 days
Mean response time: 113.3 days
90th percentile: 372.7 days
Tracked items: 55

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 924 days
Stale 30+ days: 13
Stale 90+ days: 13

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 1
Events in 7 days: 4

Top labels

  • kind/improvement (8)
  • kind/support (8)
  • kind/bug (5)
  • kind/feature (5)
  • milestone/needs-tracking (5)
  • project/community (3)
  • help wanted (2)
  • kind/documentation (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

OpenEBS Local PV LVM is a CSI driver that provisions Kubernetes persistent volumes backed by LVM2 logical volumes on individual cluster nodes.

The tool solves the problem of accessing LVM functionality within Kubernetes for workloads requiring low-latency, node-local storage. It implements the CSI specification with two components: a controller that processes volume requests and a node plugin that performs the actual LVM operations. By acting as a control plane for kernel LVM volumes without introducing a separate dataplane, it exposes LVM features like snapshots, thin provisioning, and resizing to Kubernetes applications while keeping storage and compute on the same host.

Adoption suits teams running stateful workloads such as databases or caching systems where data locality and low-latency access are critical and node failure tolerance is acceptable. The tool is lightweight and straightforward to deploy across Kubernetes distributions, working with Kubernetes 1.23 and later on most Linux distributions. It requires LVM2 on the host and works with locally attached disks, whether SSDs or HDDs. Teams should understand that volumes are node-bound with no cross-node replication, so data becomes inaccessible if the node fails.

The project maintains comprehensive documentation including quickstart guides, developer setup instructions, testing procedures, and governance documentation. Contribution guidelines and a defined release process are documented alongside a changelog tracking changes over time.