This page provides an overview of OpenEBS components and features presently in Alpha version and under active development. These features are not recommended to be used in production. We suggest you to familiarize and try these features on test clusters and reach out to OpenEBS Community if you have any queries, feedback or need help on these features.
The list of alpha features include:
- CSI Driver for Local PV - Device
- Dynamic NFS Provisioner
- OpenEBS CLI
- OpenEBS Monitoring Add-on
- Data Populator
Upgrade is not supported for features in Alpha version.
#CSI Driver for Local PV - Device
OpenEBS is developing a CSI driver for provisioning Local PVs that are backed by block devices.
For additional details and detailed instructions on how to get started with OpenEBS Local PV - Device CSI Driver please refer this Quickstart guide.
#Dynamic NFS Provisioner
OpenEBS is developing a dynamic NFS PV provisioner that can setup a new NFS server on top of any block storage.
For additional details and detailed instructions on how to get started with OpenEBS NFS PV provisioner please refer this Quickstart guide.
OpenEBS is developing a kubectl plugin for openebs called
openebsctl that can help perform administrative tasks on OpenEBS volumes and pools.
For additional details and detailed instructions on how to get started with OpenEBS CLI please refer this Quickstart guide.
#OpenEBS Monitoring Add-on
OpenEBS is developing a monitoring add-on package that can be installed via helm or kubectl for setting up a default prometheus, grafana and alert manager stack. The package also will include default service monitors, dashboards and alert rules.
For additional details and detailed instructions on how to get started with OpenEBS Monitoring Add-on please refer this Quickstart guide.
The Data populator can be used to load seed data into a Kubernetes persistent volume from another such volume. The data populator internally uses Rsync, which is a volume populator having the ability to create a volume from any rsync source.
- Decommissioning of a node in the cluster: In scenarios where a Kubernetes node needs to be decommissioned whether for upgrade or maintenance, a data populator can be used to migrate the data saved in the local storage of the node, that has to be decommissioned.
- Loading seed data to Kubernetes volumes: Data populator can be used to scale applications without using read-write many operation. The application can be pre-populated with the static content available in an existing PV.
To get more details about Data Populator, click here.
For instructions on the installation and usage of Data Populator, please refer to this Quickstart guide.