Published on searchstorage.techtarget.com. Read the full article here.
Mainstream storage products such as Catalogic CloudCasa and Hewlett Packard Enterprise SimpliVity use the Container Storage Interface (CSI) driver to provide storage on the back end for Kubernetes applications. This is different from the hyperconverged infrastructure (HCI)-like approach of cloud-native vendors such as Diamanti and Portworx (which is owned by Pure Storage), said Dave Raffo, senior analyst at Evaluator Group. Similar to how HCI works for virtual machines, compute and storage are attached to Kubernetes nodes and managed through Kubernetes such that when applications are moved across nodes, they will always have storage.
HCI allowed virtual server admins to spin up VMs without having to first provision storage through a storage admin. Cloud-native vendors are doing the same thing, but for containers and the people who work most directly with them — developers. They also provide the data services that would typically be found with storage arrays, such as encryption, deduplication, snapshots and replication.
“The people using Kubernetes are developers and cloud architects. They don’t want to deal with storage arrays, and they don’t want to deal with the people who manage storage arrays,” Raffo said.
Diamanti is targeting this audience, and the latest Spektra release is supporting what they’re using. It’s still a bit early to identify any Kubernetes deployment trends and best practices, so Diamanti’s best bet is to follow the customers’ lead, Raffo said. All the Kubernetes management vendors such as Robin Systems, Longhorn and Rancher will eventually want to support CRI-O and the three major public clouds, Raffo added.