OpenEBS - v3.4.0

Release Summary

🎉 🎉 🎉 OpenEBS 3.4 welcomes exciting new changes to our NVMe-first storage engine Mayastor with the release of v2.0.0. Jiva, cStor, LocalPV hostpath, Dynamic NFS Provision and Node Disk Manager go through another round of critical bug fixes and user enhancements. This release includes fixes for user-reported critical bugs as well as fixes and enhancements to improve the E2e test coverage.

Upgrade and Backward Incompatibilities

Please review this list prior to deciding to upgrade:

  • Kubernetes 1.21 or higher release is recommended as this release uses features of Kubernetes that will not be compatible with older Kubernetes releases. Some of the engines might require you to have a higher Kubernetes version as the CSI drivers have been upgraded to the latest versions. For example, Kubernetes 1.19.12 or higher is recommended for using Rawfile Local PV.

Component versions

OpenEBS is a collection of data engines and operators to create different types of replicated and local persistent volumes for Kubernetes Stateful workloads. Kubernetes volumes can be provisioned via CSI Drivers or using Out-of-tree Provisioners. The status of the various components as of v3.3.0 are as follows:

Change Summary

A detailed changelog is available under the component repositories listed above. Here is a quick summary of what has changed since the last release.

  • Support for Mayastor installation via the OpenEBS helm chart
  • On-demand Mayastor nexus switch-over on failure detection
  • Support for NVMe virtual path detection using NDM
  • Fixed imagePullSecrets error for LVM LocalPV helm chart
  • Update cStor PodDisruptionBudget to use policy/v1 Kubernetes API (k8s >=v1.25)
  • Update openebs/cstor-operators dependencies (Go v1.19)
  • Add Backend Volume PVC context to NFS server Deployments as labels

Show your Support

Are you using or evaluating OpenEBS? You can help OpenEBS in its journey towards becoming a CNCF Incubation project by sharing your OpenEBS story and join the league of OpenEBS Adopters.


MANY THANKS to our existing contributors and for everyone helping OpenEBS Community going. @AVRahul @Ab-hishek @Abhinandan-Purkait @IsAmrish @Pallavi-PH @ParthS007 @SeMeKh @Z0Marlin @akhilerm @anupriya0703 @avishnu @blaisedias @chriswldenyer @cjones1024 @gila @iyashu @jonathan-teh @kmova @mittachaitu @mtzaurus @mynktl @niladrih @nsathyaseelan @paulyoong @pawanpraka1 @prateekpandey14 @rajaSahil @rakeshPRaghu @satyapriyamishra222 @shovanmaity @shubham14bajpai @tiagolobocastro @vharsh @w3aman @abhilashshetty04 @rohan2794 @dsavitskiy

A very special thanks to our first-time contributors to code, tests, and docs: @hiattp, @Dentrax, @dborman-hpe, @datacore-vkumar, @jianghushinian, @WillyRL, @sinhaashish, @pchandra19, @simrankureel, @geier, @datacore-vvarakantham, @nearora-msft, @dsharma-dc, @felix1972, @dbackeus, @farcaller, @hrudaya21.



OpenEBS can be installed via kubectl or helm. Follow the installation instructions here.


The upgrade instructions for various OpenEBS engines are here.

Do not upgrade if you are using legacy cstor or jiva provisioners. You have to first migrate those to the corresponding CSI Drivers. Please reach out to us for support

Known Issues

Check our open issues uncovered through e2e and community testing.


If you are having issues in setting up or upgrade, you can contact:
- OpenEBS Community for Support on Kubernetes Slack
- Already signed up? Head to our user discussions at #openebs
- Would you like to contribute to the OpenEBS project? Head to our contributor discussions at #openebs-dev
- Raise an issue
- Subscribe and reach out on our OpenEBS CNCF Mailing lists
- For OpenEBS project updates, subscribe to OpenEBS Announcements
- For interacting with other OpenEBS users, subscribe to OpenEBS Users
- Join Community Meetings


Feb. 16, 2023, 6:43 p.m.
Register or login to:
  • 🔍View and search all OpenEBS releases.
  • 🛠️Create and share lists to track your tools.
  • 🚨Setup notifications for major, security, feature or patch updates.
  • 🚀Much more coming soon!
Continue with GitHub
Continue with Google