TiloBox
Back to directory
OpenEBS project preview

OpenEBS

Leading open source Container Attached Storage (CAS) solution for Kubernetes.

LicenseApache-2.0
GitHub stars12.5k
Last commit1 weeks ago
Tags6 topics
Container Attached StorageMayastor NvmeKubernetes CsiDevopsRust StorageGolang
Overview

Why consider OpenEBS?

OpenEBS is an open-source Container Attached Storage (CAS) platform written in Go and Rust. It provisions hyper-converged dynamic persistent volumes (Mayastor NVMe-oF engines, ZFS LocalPV, and Dynamic LocalPV) for stateful databases running on Kubernetes.

Guided learning

Learn OpenEBS by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of OpenEBS

OpenEBS attaches dedicated high-speed NVMe-oF replicated storage micro-controllers to each individual database pod.

Installation with Helm

bash
1helm repo add openebs https://openebs.github.io/openebs
2helm install openebs --namespace openebs openebs/openebs --create-namespace

OpenEBS is an Apache 2.0 licensed CNCF project.

Related tools

More options with a similar category or technology profile.

OpenEBS FAQs

OpenEBS is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

OpenEBS is listed under the Apache-2.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

OpenEBS is listed as an alternative to Portworx. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.