KUBEMOVE: Avoiding the Tragedy of the Commons

Evan Powell
MayaData
Published in
2 min readMay 19, 2019

And extending Kubernetes to cross-cluster data mobility

To the benefit of many thousands of users, Kubernetes has become almost ubiquitous and has matured in the management of stateful workloads.

One reason Kubernetes has triumphed is that it is open and provides a common set of APIs that provide an abstraction layer for cloud and on-premise operations of cloud native environments.

There are some clouds on the horizon, however. There is uncertainty over the direction of Kubernetes in management across clusters. This higher level of control and abstraction is being advanced in Kubernetes itself in cluster federation work and discussed in other projects. However commercial providers of Kubernetes based solutions are not waiting. They are moving ahead with additional functionality that extends Kubernetes for common use cases such as cross-platform data migration.

As an example, at MayaData we have extended OpenEBS and the OpenEBS Enterprise Edition to enable DMaaS or data migration as a service. Unlike many functions such as snapshots and clones that are triggered by Kubernetes API calls — the movement of data from one location to the other, or the back-up of the data, or the retrieval or similar functions — these are governed by our own APIs and control plane.

KubeMove: An Operator and API set for Kubernetes data mobility

Similarly, Google recently launched …
Read the complete article in MayaData’s Blog

--

--

Evan Powell
MayaData

Founding CEO of a few companies including StackStorm (BRCD) and Nexenta — and CEO &Chairman of OpenEBS / MayaData. ML and DevOps and Python, oh my!