OpenEBS is an open-source storage service for Kubernetes applications. OpenEBS manages the block storage and file systems based on the block storage for containers running in Kubernetes. Use OpenEBS for creating fast and resilient storage; with options for single-node, and replicated multi-node storage.

OpenEBS is a Stateful Persistent block-mode Data Storage platform with a native vSAN fabric; for Kubernetes. We are a CNCF member project. We are the largest global community of K8s storage users.

Our project team was an early pioneering inventor of K8s Container Native Storage services (we invented the term). We conceived the vision of a Stateful Persistent data platform for K8s that is tightly integrated and natively embedded into the core of K8s.

We built an innovative High-performance Enterprise grade Block-mode Hyper-converged Storage vSAN Fabric that augments the storage services of K8s with Stateful Persistence, Enterprise Data mgmt, SSD/NVMe optimized I/O services, Replicated Data volumes, Thin Provisioning, Snapshot, Clones; and many other Mission critical data storage services that don't come in K8s out-of-the-box.

OpenEBS is very popular :
Live OpenEBS systems actively report back product telemetry each day, to our Global Analytics system (unless disabled by the user).
Below are our project popularity & penetration metrics as of: 01 May 2024

🚀   OpenEBS is the #1 deployed Storage Platform for Kubernetes
⭐   We are the #1 GitHub Star ranked K8s Data Storage platform
💾   We have +49 Million Volumes deployed globally
📺   We have +9 Million Global Live Nodes
⚡   1 Million OpenEBS K8s Containers are spawned per week
😎   1.7 Million User Installations

	Our global team comes from many areas of the data storage industry. Companies like... Microsoft Azure, VMware, DELL/EMC, Brocade/Broadcom, Hitachi Vantara, INTEL, Nvidia/Mellanox, IBM, RedHat and DataCore.

OpenEBS provides enterprise-grade data management for Kubernetes clusters, with five different storage engines (four single-node and one replicated) that meet a range of use cases for Kubernetes users. The five engines are summarized in the table below:

Engine	Local PV HostPath	Local PV ZFS	Local PV LVM	Local PV Rawfile	Replicated PV Mayastor
Type	Single-node	Single-node	Single-node	Single-node	Multi-node
What is it for?	Replacement for in-Tree Kubernetes CSI HostPath	Storage engine for ZFS managed backend storage	Storage engine for LVM2 managed backend storage	Experimental engine for using an extent file as block storage	General purpose replicated enterprise storage
Designed for	Developers or DevOps	ZFS users and production deployments	LVM2 users and production deployments	Developers	Enterprises and production deployments
Features	Everything in Kubernetes HostPath, plus: - Dynamic provisioning, Zero configuration, No CSI driver	Provision ZFS datasets, Provision ZFS volumes, Dynamic provisioning, ZFS resilience, ZFS RAID protection, CSI driver	Provision LVM2 volumes, Dynamic provisioning, LVM2 RAID protection, CSI driver	Provision file system from local files as persistent volumes, CSI driver	Replicated storage NVMe / RDMA, Snapshots, Clones, High availability, CSI driver
Status	Stable, deployable in PROD	Stable, deployable in PROD	Stable, deployable in PROD	Beta, undergoing evaluation & integration	Stable, deployable in PROD
Current Version				release: v0.70

We are an Ultra modern Data storage platform stack that is strongly aligned with the cutting-edge direction of storage use cases in the K8s industry. openEBS is designed to facilitate modern K8s datastore architectures, key K8s I/O patterns, K8s data access methods, K8s data use-cases and where K8s Datastore applications are heading.

OpenEBS is optimized for NVMe and SSD Flash storage media and integrates ultra-modern cutting-edge high-performance storage technologies at its core.

☑️   It uses the High performance SPDK storage stack - (SPDK is an open-source NVMe project initiated by INTEL)
☑️   The hyper-modern IO_Uring Linux Kernel Async polling-mode I/O Interface - (fastest kernel I/O mode possible)
☑️   Native abilities for RDMA and Zero-Copy I/O
☑️   NVMe-oF TCP Block storage Hyper-converged data fabric
☑️   Block layer volume replication
☑️   Logical volumes and Diskpool based data management
☑️   a Native high performance Blobstore
☑️   Native Block layer Thin provisioning
☑️   Native Block layer Snapshots and Clones

LEGACY consists of Data-Engines that we experimented with early on. These Data-Engines have a number of open-source
technologies embedded inside them, and are a great intro into the world of simple K8s storage services. LEGACY helped
us learn, iterate, and develop our core storage K8s strategy, as well as discern how users want & need to interact with
K8s storage services. LEGACY also helped to reveal key areas within K8s that are lacking in storage/datastore services,
what areas of K8s we could optimize; and how we can provide the best value into the various K8s storage layers.

There are multiple Storage Engines within LEGACY:

Our 2024 Roadmap is here It defines a rich set of new features that are planned for 2024.
Please review this roadmap and feel free to pass back any feedback on it, as well as recommend and suggest new ideas. We welcome all of your feedback.

OpenEBS is committed to bringing Enterprise-grade data management to Kubernetes. More people trust OpenEBS with their enterprise's data than any other storage platform.

We centralize all our community documentation in the Community repo. All sub-projects within the organization follow the same umbrella policies, except where stated in the sub-project readme.

OpenEBS holds a monthly community meeting via Zoom on the last Thursday of the month, at 14:00 UTC.
The next meeting is on: Thursday 26 September, at 14:00 UTC
Meeting Link: https://us05web.zoom.us/j/87535654586?pwd=CigbXigJPn38USc6Vuzt7qSVFoO79X.1
Starting in August 2024, the meetings will be recorded and posted on YouTube. Check here

Maintainers meet weekly and minute their meetings. A public record of the meetings is here. See Vision for more detail on what we do, Governance for how we do it, and Contributing for how to get involved

We are actively looking for new contributors and maintainers. Want to get involved, but not sure how? Please email the OpenEBS maintainers at [email protected]