openebs/mayastor

Dynamically provision Stateful Persistent Replicated Cluster-wide Fabric Volumes & Filesystems for Kubernetes that is provisioned from an optimized NVME...

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

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

openebs/mayastor has 1k+ stars and 100+ forks on GitHub, is written in Rust, and was last pushed on Oct 16, 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 August 27th, 2019
Open Issues & Pull Requests: 80 (+0)
GitHub issues: Enabled
Number of forks: 144
Total Stargazers: 1,071 (+0)
Total Subscribers: 23 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.8 hours
Mean response time: 12.3 days
90th percentile: 9.9 days
Tracked items: 154

How this project is maintained

78% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 72% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 58
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 566 days
Stale 30+ days: 52
Stale 90+ days: 44

Recent activity

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

Top labels

  • kind/bug (37)
  • kind/improvement (27)
  • triage/needs-information (15)
  • kind/documentation (8)
  • help wanted (5)
  • area/upgrade (3)
  • good first issue (3)
  • needs-triage (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Mayastor is a cloud-native storage data plane for Kubernetes that dynamically provisions persistent replicated volumes backed by an optimized NVMe and SPDK storage stack.

Mayastor addresses the challenge of providing low-latency storage to Kubernetes workloads while abstracting away differences between storage systems. It decouples applications from storage implementation details through a declarative data plane written in Rust. The architecture separates concerns into a control plane—built around a core agent, RESTful API, disk pool operator, and CSI-compliant provisioner—and a data plane consisting of I/O Engine instances running on each storage node. The data plane's Nexus component attaches to storage resources and presents them to workloads, while local storage pools can be carved into logical volumes and shared across nodes via NVMe over Fabrics.

Mayastor suits teams running Kubernetes clusters that need high-performance storage without vendor lock-in, particularly those with existing storage infrastructure they want to unify rather than replace. It is designed for converged and segregated storage deployments, and supports specialized container runtimes like Firecracker microVMs and Kata Containers through vhost-user storage access. The tool also enables programmatic storage access, allowing applications to write directly to block devices. Organizations should evaluate Mayastor if they prioritize low latency, need to work with heterogeneous storage systems, or require storage abstraction across a cluster without painful data migration.

The project maintains active development with regular commits across both the core data plane and related control plane repositories. Work spans multiple areas including storage device handling, Kubernetes integration, and the Rust-based I/O engine implementation. The codebase shows ongoing refinement of the Nexus component and storage pool management, with contributions addressing both new features and operational stability.