Most popular & widely deployed Open Source Container Native Storage platform for Stateful Persistent Applications on Kubernetes.
APACHE-2.0 License
Bot releases are hidden (Show)
This patch fixes an issue with Replicated PV Mayastor on older Linux kernels. Click here to go to the v4.0.0 release notes.
Published by kmova 6 months ago
Containerized Attached Storage for Kubernetes
Published by niladrih 6 months ago
OpenEBS 4.0.0 is a major milestone towards simplification of the overall user experience. With the guidance of the governing body CNCF (Cloud Native Computing Foundation), significant changes have been made to the structure and architecture of OpenEBS. These changes were deemed necessary for the long-term health and maintenance of the project, tracked with an issue here.
In a nutshell, the changes can be broadly classified into the following categories:
These are in addition to the vast majority of super cool features and enhancements to the local and replicated storage solutions, that OpenEBS is well-known for.
With this release, OpenEBS plans to re-enter the CNCF landscape as a Sandbox project and establish itself as the most popular and leading cloud-native storage solution for Kubernetes stateful workloads.
Prior to the release 4.0.0, OpenEBS had the following solutions or engines:
In 4.0.0, the maintainers have decided to trim down the above list, for improved focus and sustained future maintenance. This was a tough but strategic decision. Several factors like adoption, relevance, available expertise, and a bit of common sense (π) have been taken into account in the retention of the engines and technologies that OpenEBS wants to move forward with.
The new and re-organized structure of OpenEBS comprises the following:
With the inclusion of the above engines, OpenEBS can cater to an almost 900,000 strong user-base. For the users of the legacy engines (those will soon be deprecated), we would like to offer our whole-hearted gratitude for being the early adopters and supporters of OpenEBS and contributing to the maturity that OpenEBS has reached today. Migration procedures are documented here to migrate data from legacy OpenEBS engines to OpenEBS 4.0.0 storage.
βΉοΈ Info
The code and dependent repositories associated with the legacy deprecated projects and engines will soon be transferred from GitHub openebs organization to GitHub openebs-archive organization. This issue here provides the background.
Before 4.0.0, OpenEBS had its technical documentation distributed across two websites:
Release 4.0.0 integrates OpenEBS Local and Replicated Storage documentation, and publishes them in the https://openebs.io/docs website. The release also cleans up the contents related to the legacy engines that are now deprecated.
Since the documentation is versioned, users of legacy engines would still be able to view the contents as follows:
OpenEBS 4.0.0 Helm chart is the supported way to install both OpenEBS Local and Replicated engines. The OpenEBS 4.0.0 Helm chart bundles sub-charts for the following components:
All of the above storage components are installed as part of the default installation. The Helm chart provides an option to exclude Mayastor, for users interested in only Local PV storage.
βΉοΈ Info
The operator.yaml way of installing individual OpenEBS engines has now been deprecated. It is also not recommended to independently install the various Helm sub-charts.
OpenEBS is a collection of data engines and operators to create different types of Local and Replicated Persistent Volumes (PVs) for Kubernetes stateful workloads. Kubernetes PVs can be provisioned via Container Storage Interface (CSI) Drivers or using Out-of-tree Provisioners. The status of the various components as of v4.0.0 are as follows:
A detailed changelog is available under the component repositories listed above. Here is a quick summary of what has changed since the last release.
βΉοΈ Info
There will be no version updates for the auxiliary components like the Velero-plugin, Monitoring, and Data Populator in this release. There will be focused changes on removing legacy support in these projects before releasing updated versions for these projects.
Before deciding to upgrade, review the list below:
Published by kmova 6 months ago
Containerized Attached Storage for Kubernetes
Published by niladrih 10 months ago
π π π OpenEBS 3.10 introduces new Mayastor features, and bug fixes. LocalPV-Provisioner (hostpath), NFS-Provisioner, ZFS-LocalPV and LVM-LocalPV welcome enhancements which improve QoL.
Please review this list prior to deciding to upgrade:
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.9.0 are as follows:
A detailed changelog is available under the component repositories listed above. Here is a quick summary of what has changed since the last release.
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. @Abhinandan-Purkait @avishnu @blaisedias @chriswldenyer @niladrih @tiagolobocastro @w3aman @abhilashshetty04 @rohan2794 @dsavitskiy @sinhaashish @datacore-vvarakantham @dsharma-dc @hrudaya21 @pchandra19 @milanhajek @r1jt @AJDatacore @avishnu
A very special thanks to our first-time contributors to code, tests, and docs: @ukd1 @trunet @omric-runai @emiran-orange @cmontemuino @maxs-rose @MingZhang-YBPS @njuptlzf @testwill @pentago
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
Check our open issues uncovered through e2e and community testing.
Check out the Mayastor release notes for known Mayastor issues.
If you are having issues in setting up or upgrade, you can contact:
Published by niladrih about 1 year ago
π π π OpenEBS 3.9 introduces new Mayastor features, and bug fixes. LVM LocalPV sees new enhancements to monitoring, refactors and other bug fixes.
Please review this list prior to deciding to upgrade:
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.9.0 are as follows:
A detailed changelog is available under the component repositories listed above. Here is a quick summary of what has changed since the last release.
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. @Abhinandan-Purkait @avishnu @blaisedias @chriswldenyer @mtzaurus @niladrih @tiagolobocastro @w3aman @abhilashshetty04 @rohan2794 @dsavitskiy @sinhaashish @datacore-vvarakantham @dsharma-dc @hrudaya21 @pchandra19 @milanhajek @r1jt @AJDatacore @avishnu
A very special thanks to our first-time contributors to code, tests, and docs: @Rajpratik71 @dnugmanov @kro-cat @TECHNOFAB11
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
Check our open issues uncovered through e2e and community testing.
Check out the Mayastor release notes for known Mayastor issues.
If you are having issues in setting up or upgrade, you can contact:
Published by niladrih about 1 year ago
π π π OpenEBS 3.8 introduces new Mayastor features, and bug fixes. All CSI LocalPV engines, cStor and Jiva now support Kuberenetes v1.27.
Please review this list prior to deciding to upgrade:
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.8.0 are as follows:
A detailed changelog is available under the component repositories listed above. Here is a quick summary of what has changed since the last release.
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. @Abhinandan-Purkait @avishnu @blaisedias @chriswldenyer @mtzaurus @niladrih @tiagolobocastro @w3aman @abhilashshetty04 @rohan2794 @dsavitskiy @sinhaashish @datacore-vvarakantham @dsharma-dc @hrudaya21 @pchandra19 @milanhajek @vharsh
A very special thanks to our first-time contributors to code, tests, and docs: @AJDatacore @jnels124 @aceat64 @cxfcxf
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
Check our open issues uncovered through e2e and community testing.
Check out the Mayastor release notes for known Mayastor issues.
If you are having issues in setting up or upgrade, you can contact:
Published by niladrih over 1 year ago
π π π OpenEBS 3.7 introduces new Mayastor features, and bug fixes. The LocalPV CSI engines get dependency updates, optimisations and performance updates.
Please review this list prior to deciding to upgrade:
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.6.0 are as follows:
A detailed changelog is available under the component repositories listed above. Here is a quick summary of what has changed since the last release.
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. @Abhinandan-Purkait @anupriya0703 @avishnu @blaisedias @chriswldenyer @mtzaurus @niladrih @tiagolobocastro @w3aman @abhilashshetty04 @rohan2794 @dsavitskiy @sinhaashish @datacore-vvarakantham @dsharma-dc @hrudaya21 @shubham14bajpai
A very special thanks to our first-time contributors to code, tests, and docs: @lowjoel, @barkbay
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
Check our open issues uncovered through e2e and community testing.
Check out the Mayastor release notes for known Mayastor issues.
If you are having issues in setting up or upgrade, you can contact:
Published by niladrih over 1 year ago
π π π OpenEBS 3.6 welcomes exciting new changes to our NVMe-first storage engine Mayastor with the release of v2.1.0.
Please review this list prior to deciding to upgrade:
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.6.0 are as follows:
A detailed changelog is available under the component repositories listed above. Here is a quick summary of what has changed since the last release.
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. @Abhinandan-Purkait @anupriya0703 @avishnu @blaisedias @chriswldenyer @mtzaurus @niladrih @tiagolobocastro @w3aman @abhilashshetty04 @rohan2794 @dsavitskiy
A very special thanks to our first-time contributors to code, tests, and docs: @sinhaashish, @datacore-vvarakantham, @nearora-msft, @dsharma-dc, @felix1972, @hrudaya21, @xUnholy.
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
Check our open issues uncovered through e2e and community testing.
Check out the Mayastor release notes for known Mayastor issues.
If you are having issues in setting up or upgrade, you can contact:
Published by niladrih over 1 year ago
πππ This release adds stability and QoL changes to the Mayastor storage engine. Read the release notes here.
Please review this list prior to deciding to upgrade:
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.5.0 are as follows:
A detailed changelog is available under the component repositories listed above. Here is a quick summary of what has changed since the last release.
Thank you @nkwangleiGIT for sharing your OpenEBS adoption story.
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. @Abhinandan-Purkait
@anupriya0703 @avishnu @blaisedias @chriswldenyer @mtzaurus @mynktl @niladrih @nsathyaseelan @tiagolobocastro @w3aman @abhilashshetty04 @rohan2794 @dsavitskiy
A very special thanks to our first-time contributors to code, tests, and docs: @ryandellolio
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
Check our open issues uncovered through e2e and community testing.
Check out the Mayastor release notes for known Mayastor issues.
If you are having issues in setting up or upgrade, you can contact:
Published by niladrih over 1 year ago
π π π 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.
Please review this list prior to deciding to upgrade:
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.4.0 are as follows:
A detailed changelog is available under the component repositories listed above. Here is a quick summary of what has changed since the last release.
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. @Ab-hishek @Abhinandan-Purkait @Pallavi-PH @akhilerm @anupriya0703 @avishnu @blaisedias @chriswldenyer @mittachaitu @mtzaurus @mynktl @niladrih @nsathyaseelan @paulyoong @rajaSahil @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
Check our open issues uncovered through e2e and community testing.
Check out the Mayastor release notes for known Mayastor issues.
If you are having issues in setting up or upgrade, you can contact:
Published by pawanpraka1 over 2 years ago
π π π OpenEBS 3.3 is another maintenance release focused on code, tests and build refactoring along with some 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.
Deprecation Notice: Jiva and cStor out-of-tree external
provisioners are deprecated now in favor of the corresponding CSI Drivers. The out of tree provisioners for Jiva and cStor will stop working from Kubernetes 1.22 and forward as the version of the custom resources used by those provisioners will be deprecated. We strongly recommend you plan for migrating your volumes to cStor CSI or Jiva CSI as early as possible.
If you have any questions or need help with the migration please reach out to us on our Kubernetes Community slack channel #openebs.
Please review this list prior to deciding to upgrade:
cstor-pool-arm64:x.y.x
should be replaced with corresponding multi-arch image cstor-pool:x.y.x
.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:
A detailed Changelog is available under the component repositories listed above. The focus was to close on the refactoring and maintenance-related activities and a few bug fixes that were required for some of the components to be declared GA or beta. Here is a quick summary of what has changed since the last release.
Thank you @cxfcxf (Xuefeng Chen) for sharing your OpenEBS Adoption story.
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
A very special thanks to our first-time contributors to code, tests, and docs: @nkwangleiGIT, @dong-liuliu, @croomes, @neoaggelos, @jtcarnes, @abhilashshetty04, @rohan2794, @hickersonj.
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
Check our open issues uncovered through e2e and community testing.
If you are having issues in setting up or upgrade, you can contact:
Published by pawanpraka1 over 2 years ago
π π π OpenEBS 3.2 is another maintenance release focused on code, tests and build refactoring along with some 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.
Deprecation Notice: Jiva and cStor out-of-tree external
provisioners are deprecated now in favor of the corresponding CSI Drivers. The out of tree provisioners for Jiva and cStor will stop working from Kubernetes 1.22 and forward as the version of the custom resources used by those provisioners will be deprecated. We strongly recommend you plan for migrating your volumes to cStor CSI or Jiva CSI as early as possible.
If you have any questions or need help with the migration please reach out to us on our Kubernetes Community slack channel #openebs.
Please review this list prior to deciding to upgrade:
cstor-pool-arm64:x.y.x
should be replaced with corresponding multi-arch image cstor-pool:x.y.x
.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.2.0 are as follows:
A detailed Changelog is available under the component repositories listed above. The focus was to close on the refactoring and maintenance-related activities and a few bug fixes that were required for some of the components to be declared GA or beta. Here is a quick summary of what has changed since the last release.
In-Progress items
Thank you @RytisLT(Rytis Ilciukas) for sharing your OpenEBS Adoption story.
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
A very special thanks to our first-time contributors to code, tests, and docs: @csschwe, @karanssj4, @reitermarkus, @MukulKolpe, @gozssky, @adamcharnock.
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
Check our open issues uncovered through e2e and community testing.
If you are having issues in setting up or upgrade, you can contact:
Published by pawanpraka1 almost 3 years ago
π π π OpenEBS 3.1 is a maintenance release focused on code, tests and build refactoring along with some 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.
Deprecation Notice: Jiva and cStor out-of-tree external
provisioners are deprecated now in favor of the corresponding CSI Drivers. The out of tree provisioners for Jiva and cStor will stop working from Kubernetes 1.22 and forward as the version of the custom resources used by those provisioners will be deprecated. We strongly recommend you plan for migrating your volumes to cStor CSI or Jiva CSI as early as possible.
If you have any questions or need help with the migration please reach out to us on our Kubernetes Community slack channel #openebs.
Please review this list prior to deciding to upgrade:
cstor-pool-arm64:x.y.x
should be replaced with corresponding multi-arch image cstor-pool:x.y.x
.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.1.0 are as follows:
A detailed Changelog is available under the component repositories listed above. The focus was to close on the refactoring and maintenance-related activities and a few bug fixes that were required for some of the components to be declared GA or beta. Here is a quick summary of what has changed since the last release.
Thank you @trathborne(Tom Rathborne), @jggc(Jean-Gab) for sharing your OpenEBS Adoption story.
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
A very special thanks to our first-time contributors to code, tests, and docs: @jdkramhoft, @ianroberts, @davidkarlsen, @abhisheksinghbaghel, @vakul-gupta-flp, @shazadbrohi, @jggc.
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
Check our open issues uncovered through e2e and community testing.
If you are having issues in setting up or upgrade, you can contact:
Published by kmova about 3 years ago
π π π OpenEBS 3.0 is a culmination of efforts geared towards laying the foundation for making it easier to onboard and accept community contributions, making each of the data engine operators ready for future Kubernetes releases, making it easy to manage, and troubleshoot various data engines. This has been achieved via migration to the latest Kubernetes constructs, ease of use improvements, bug fixes and most importantly refactoring the control plane and e2e test suites to independently enhance and release each of the engines.
Deprecation Notice: Jiva and cStor out-of-tree external
provisioners will be deprecated by Dec 2021 in favor of the corresponding CSI Drivers. The out of tree provisioners for Jiva and cStor will stop working from Kubernetes 1.22 and forward as the version of the custom resources used by those provisioners will be deprecated. We strongly recommend you plan for migrating your volumes to cStor CSI or Jiva CSI as early as possible.
If you have any questions or need help with the migration please reach out to us on our Kubernetes Community slack channel #openebs.
Please review this list prior to deciding to upgrade:
cstor-pool-arm64:x.y.x
should be replaced with corresponding multi-arch image cstor-pool:x.y.x
.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.0.0 are as follows:
A detailed Changelog is available under the component repositories listed above. The focus was to close on the refactoring and maintenance-related activities and a few bug fixes that were required for some of the components to be declared GA or beta. Here is a quick summary of what has changed since the last release.
Thank you @turowicz(Surveily), @WillyRL(Teknologi Anak Rantau Indonesia), @Somsubhra1, @t3hmrman for sharing your OpenEBS Adoption story.
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
A very special thanks to our first-time contributors to code, tests, and docs: @burntcarrot, @aamirqs, @sbidoul, @dsavitskiy, @almas33, @liuminjian, @zeenix, @Nivedita-coder, @fengye87, @Abhishek-kumar09, @Amishakumari544, @eripa, @Quarky9, @tathougies, @omeiirr, @g-linville, @rweilg
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
Check our open issues uncovered through e2e and community testing.
If you are having issues in setting up or upgrade, you can contact:
Published by kmova over 3 years ago
OpenEBS v2.11 is another maintenance release before moving towards 3.0 primarily focusing on enhancing the E2E tests, build, release workflows, and documentation. This release also includes enhancements to improve the user experience and fixes for bugs reported by users and E2E tools. There has been some significant progress made on the alpha features as well.
Deprecation Notice: Jiva and cStor out-of-tree external
provisioners will be deprecated by Dec 2021 in favor of the corresponding CSI Drivers. The out of tree provisioners for Jiva and cStor will stop working from Kubernetes 1.22 and forward as the version of the custom resources used by those provisioners will be deprecated. We strongly recommend you plan for migrating your volumes to cStor CSI or Jiva CSI as early as possible.
If you have any questions or need help with the migration please reach out to us on our Kubernetes Community slack channel #openebs.
kubectl openebs get bd
)cstor-pool-arm64:x.y.x
should be replaced with corresponding multi-arch image cstor-pool:x.y.x
.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 v2.11.0 are as follows:
Thank you @survivant (Jerabi Inc.) for sharing your OpenEBS Adoption story.
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.
A very special thanks to our first-time contributors to code, tests, and docs: @RolandMa1986, @hrenard, @huangfangfeng
OpenEBS can be installed via kubectl
or helm3
. Follow the installation instructions here.
The upgrade instructions for various OpenEBS engines are here
Check our open issues uncovered through e2e and community testing.
If you are having issues in setting up or upgrade, you can contact:
Published by kmova over 3 years ago
OpenEBS v2.10 is another maintenance release before moving towards 3.0 primarily focusing on enhancing the E2e tests, build, release workflows, and documentation. This release also includes enhancements to improve the user experience and fixes for bugs reported by users and E2e tools. There has been some significant progress made on the alpha features as well.
Deprecation Notice: Jiva and cStor out-of-tree external
provisioners will be deprecated by Dec 2021 in favor of the corresponding CSI Drivers. The out of tree provisioners for Jiva and cStor will stop working from Kubernetes 1.22 and forward as the version of the custom resources used by those provisioners will be deprecated. We strongly recommend you plan for migrating your volumes to cStor CSI or Jiva CSI as early as possible.
If you have any questions or need help with the migration please reach out to us on our Kubernetes Community slack channel #openebs.
A very special thanks to @cncf and 2021 LFX Mentees @ParthS007, @rahul799 for contributing to the above features!!
values.yaml
to install the specific projects. You can read more about these additional options here.btrfs
formatted volume. https://github.com/openebs/lvm-localpv/pull/85
cstor-pool-arm64:x.y.x
should be replaced with corresponding multi-arch image cstor-pool:x.y.x
.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 v2.10.0 are as follows:
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.
A very special thanks to our first-time contributors to code, tests, and docs: @Pallavi-PH, @sreeharimohan, @Atharex, @rakeshPRaghu, @Sanjay1611 @pankaj892
OpenEBS can be installed via kubectl
or helm3
. Follow the installation instructions here.
The upgrade instructions for various OpenEBS engines are here
Check our open issues uncovered through e2e and community testing.
If you are having issues in setting up or upgrade, you can contact:
Published by kmova over 3 years ago
OpenEBS v2.9 is another maintenance release before moving towards 3.0 primarily focusing on enhancing the E2e tests and build/release workflows. This release includes fixes for user-reported critical bugs as well as fixes and enhancements to improve the E2e test coverage. There has been some significant progress made on the alpha features as well.
openebs.io/nodeid
to set the node affinity for the provisioned volume. By default, the value will be the same as kubernetes.io/hostname
. Using a custom label like this will help in quickly migrating the volumes to a new node in cases where a node fails and the user needs to move the underlying disks to a new node in the cluster. After moving the disks, the user can set the openebs.io/nodeid
with the value used in the previous node. (https://github.com/openebs/zfs-localpv/issues/304). You can read more about this feature here.restApiTimeout
field in VolumeSnapshotLocation. See example. (https://github.com/openebs/velero-plugin/issues/148)hyperkube
image. Moved to kubectl
images from bitnami. (https://github.com/openebs/openebs/issues/3383)ubuntu 16.04
as the base image. Moved to ubuntu 18.04
.(https://github.com/openebs/openebs/issues/3386)cstor-pool-arm64:x.y.x
should be replaced with corresponding multi-arch image cstor-pool:x.y.x
.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 v2.9.0 are as follows:
APP VERB NOUN
format. Example: kubectl openebs describe volume [cstor-pv-name]
kubectl openebs get pools
Thank you @weizenberg from Lannister Investments LTD for becoming a public reference and supporter of OpenEBS by sharing your use case on ADOPTERS.md
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.
We are excited to welcome our new maintainers Sjors Gielen for the cStor engine and Yashpal for Local PV engines.
A very special thanks to our first-time contributors to code, tests, and docs: @jj-2020, @abhiTamrakar, @ParthS007, @Abhinandan-Purkait, @JanKoehnlein, @soniasingla, @rahulgrover99, @nisarg1499, @asquare14, @rajaSahil, @arcolife, @satyapriyamishra222, @rahul799, @is-ashish
OpenEBS can be installed via kubectl
or helm3
. Follow the installation instructions here.
The upgrade instructions for various OpenEBS engines are here
Check our open issues uncovered through e2e and community testing.
If you are having issues in setting up or upgrade, you can contact:
Published by kmova over 3 years ago
OpenEBS v2.8 is the another maintenance release before moving towards 3.0, and includes fixes and enhancements geared towards migrating non CSI volumes to CSI and improvements to E2e. This release also includes some key user-requested bug fixes and enhancements.
Important Announcement: KubeCon + CloudNativeCon Europe 2021 will take place May 4 - 7, 2021! Meet the OpenEBS maintainers and end-users to learn more about OpenEBS Roadmap, implementation details, best practices, and more. RSVP to one of the following events:
The latest release versions of each of the engine are as follows:
Kubernetes 1.18 or higher release is recommended as this release contains the following updates that will not be compatible with older Kubernetes releases.
If you are upgrading from a version of cStor operators older than 2.6 to this version, you will need to manually delete the cStor CSI driver object prior to upgrading. kubectl delete csidriver cstor.csi.openebs.io
. For complete details on how to upgrade your cStor operators, see https://github.com/openebs/upgrade/blob/master/docs/upgrade.md#cspc-pools.
The CRD API version has been updated for the cStor custom resources to v1. If you are upgrading via the helm chart, you might have to make sure that the new CRDs are updated. https://github.com/openebs/cstor-operators/tree/master/deploy/helm/charts/crds
Thank you @jayheinlein from Sharecare, Inc. for becoming a public reference and supporter of OpenEBS by sharing your use case on ADOPTERS.md
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.
We are excited to welcome Harsh Thakur as maintainer for Local PV engines.
A very special thanks to our first-time contributors to code, tests, and docs: @etherealvisage, @ntdt, @centromere, @watcher00090, @t3hmrman
kubectl apply -f https://openebs.github.io/charts/2.8.0/openebs-operator.yaml
helm repo add openebs https://openebs.github.io/charts
helm repo update
helm install --namespace openebs --name openebs openebs/openebs --version 2.8.0
For more details refer to the documentation at https://docs.openebs.io/
Upgrade to 2.8 is supported only from 1.0 or higher and follows a similar process as earlier releases. Detailed steps are provided here.
For upgrading from releases prior to 1.0, please refer to the respective release upgrade here.
Note: The community e2e pipelines verify upgrade testing only from non-deprecated releases (1.7 and higher) to 2.8. If you are running on release older than 1.7, OpenEBS recommends you upgrade to the latest version as soon as possible.
If you are having issues in setting up or upgrade, you can contact:
For a more comprehensive list of open issues uncovered through e2e and community testing, please refer to open issues. If you are using the cStor Storage Engine, please review the following before upgrading to this release.
Init
.Published by kmova over 3 years ago
OpenEBS v2.7 is a maintenance release geared towards preparing for better structuring of the code and improving on the E2e frameworks. This release also includes some key user-requested bug fixes and enhancements.
The latest release versions of each of the engine are as follows:
Here are some of the key highlights in this release.
Kubernetes 1.17 or higher release is recommended as this release contains the following updates that will not be compatible with older Kubernetes releases.
If you are upgrading from a version of cStor operators older than 2.6 to this version, you will need to manually delete the cStor CSI driver object prior to upgrading. kubectl delete csidriver cstor.csi.openebs.io
. For complete details on how to upgrade your cStor operators, see https://github.com/openebs/upgrade/blob/master/docs/upgrade.md#cspc-pools.
The CRD API version has been updated for the cStor custom resources to v1. If you are upgrading via the helm chart, you might have to make sure that the new CRDs are updated. https://github.com/openebs/cstor-operators/tree/master/deploy/helm/charts/crds
Thank you Armel Soro, Art Win, @ssytnikov18 from Verizon Media, Mike T, grouchojeff for becoming a public reference and supporter of OpenEBS by sharing your use case on ADOPTERS.md
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.
We are excited to welcome Praveen Kumar G T as maintainer for Local PV engines.
A very special thanks to our first-time contributors to code, tests, and docs: @luizcarlosfaria, @Z0Marlin, @iyashu, @dyasny, @hanieh-m, @si458, @Ab-hishek
kubectl apply -f https://openebs.github.io/charts/2.7.0/openebs-operator.yaml
helm repo add openebs https://openebs.github.io/charts
helm repo update
helm install --namespace openebs --name openebs openebs/openebs --version 2.7.0
For more details refer to the documentation at https://docs.openebs.io/
Upgrade to 2.7 is supported only from 1.0 or higher and follows a similar process as earlier releases. Detailed steps are provided here.
For upgrading from releases prior to 1.0, please refer to the respective release upgrade here.
Note: The community e2e pipelines verify upgrade testing only from non-deprecated releases (1.6 and higher) to 2.7. If you are running on release older than 1.6, OpenEBS recommends you upgrade to the latest version as soon as possible.
If you are having issues in setting up or upgrade, you can contact:
For a more comprehensive list of open issues uncovered through e2e and community testing, please refer to open issues. If you are using the cStor Storage Engine, please review the following before upgrading to this release.
Init
.