The second chapter of Container Attached Storage — What’s next?
In this blog, we discuss what’s next — at least from our perspective — in the overall space of container attached or Kubernetes native storage services. While there is a lot of discussions recently about OpenEBS joining the CNCF — and Evan Powell penned an article for the CNCF.io blog updating the container attached storage space — and we are also talking of course about what's coming in OpenEBS 1.0 — in this blog I want to go into a little depth about three areas of progress that together might be called the second chapter of container attached storage:
- Data mobility — what are we doing to further free users from cloud and storage lock-in and what might the community do as well?
- Pluggable storage engines FTW — Two new storage engines are hitting in the OpenEBS community, LocalPV now in beta and a rust based storage engine in alpha
- Chaos for assurance — our OpenSource chaos engineering project Litmus has been enhanced with operators to run more easily and is fundamental to our vision for an adaptive multi-cloud data layer
We are seeing more and more word of mouth by users in and around the OpenEBS community. And that’s crucial because word of mouth is what powers projects like OpenEBS committed to using Kubernetes itself as a data platform. Please do stay in touch and spread the word about this approach.
Early access to data mobility — Announcing DMaaS Beta
Data Migration as a Service or DMaaS helps users to move their workloads from one cluster to another cluster or from one namespace to another in the same cluster. Common use cases include rolling upgrades of your underlying Kubernetes or of the workloads on top such as Kafka. We also see users leveraging DMaaS to shift workloads onto different Kubernetes environments as well, such as that much-discussed multi-cloud use case. Just like OpenEBS has won some awareness as the simplest to run storage and storage services for your Kubernetes whether on-premise or in the cloud — our design philosophy for DMaaS is simplicity first. We want DMaaS to fade into the background as a primitive that just works.
How does DMaaS work?
DMaaS leverages the …
