OpenEBS is containerized block storage written in Go for cloud native and other environments w/ per container (or pod) QoS SLAs, tiering and replica policies across AZs and environments, and predictable and scalable performance.
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.


Build Status Docker Pulls Releases Slack Twitter

OpenEBS enables the use of containers for mission-critical, persistent workloads. OpenEBS is containerized storage and related storage services.

OpenEBS allows you to treat your persistent workload containers, such as DBs on containers, just like other containers. OpenEBS itself is deployed as just another container on your host and enables storage services that can be designated on a per pod, application, cluster or container level, including:

  • Data persistence across nodes, dramatically reducing time spent rebuilding Cassandra rings for example.
  • Synchronization of data across availability zones and cloud providers.
  • Use of commodity hardware plus a container engine to deliver so called container attached block storage.
  • Integration with Kubernetes, so developer and application intent flows into OpenEBS configurations automatically.
  • Management of tiering to and from S3 and other targets.

Our vision is simple: let storage and storage services for persistent workloads be fully integrated into the environment and hence can be managed automatically that it almost disappears into the background as just yet another infrastructure service that just works.

Why OpenEBS Scales

OpenEBS can scale to include an arbitrarily large number of containerized storage controllers. Thanks in part to some advancements in the metadata management which remove a common bottleneck to scaling out storage performance.

Installation and Getting Started

OpenEBS can be setup in few easy steps. You can get going on your choice of Kubernetes cluster by having open-iscsi installed on the Kubernetes nodes and running the openebs-operator using kubectl.

Start the OpenEBS Services using operator

# apply this yaml
kubectl apply -f

Apply OpenEBS StorageClasses

# apply this yaml
kubectl apply -f

You could also follow our QuickStart Guide.

OpenEBS can be deployed on any Kubernetes cluster - either in cloud, on-premise or developer laptop (minikube). Please follow our OpenEBS Setup documentation. Also, we have a Vagrant environment available that includes a sample Kubernetes deployment and synthetic load that you can use to simulate the performance of OpenEBS. You may also find interesting the related project called Litmus ( which helps with chaos engineering for stateful workloads on Kubernetes.


We are approaching beta stage with active development underway. See our Project Tracker for more details. Please note that as of June 2018 we have cStor which is about to be released for additional funcitons and somewhat improved performance; please contact us on Slack if you are interested in this engine.


OpenEBS welcomes your feedback and contributions in any form possible.

  • Join us at Slack
  • Want to raise an issue?
    • If it is a generic (or not really sure), you can still raise it at issues
    • Project (repository) specific issues also can be raised at issues and tagged with the individual repository labels like repo/maya.
  • Want to help with fixes and features?

Show me the Code

This is a meta-repository for OpenEBS. The source code is available at the following locations:

  • The source code for the initial storage engine is under openebs/jiva.
  • The storage orchestration source code is under openebs/maya.
  • While jiva and maya contain significant chunks of source code, some of the orchestration and automation code is also distributed in other repositories under the OpenEBS organization.

Please start with the pinned repositories or with OpenEBS Architecture document.


OpenEBS is developed under Apache 2.0 license at the project level. Some components of the project are derived from other open source projects like Nomad, Longhorn and are distributed under their respective licenses.