CockroachDB is a cloud-native SQL database that features both scalability and consistency. The database is designed to withstand data center failures by deploying multiple instances of symmetric nodes in a cluster consisting of several machines, disks, and data centers. Kubernetes’ built-in capabilities to scale and survive node failures as extended by Container Attached Storage make it well suited to orchestrate CockroachDB’s databases. CockroachDB can be used for SQL semantics & ACID consistency with Kubernetes.
Mayadata’s OpenEBS works well with any operator that helps to run CockroachDB on Kubernetes
The CockroachDB Kubernetes Operator deploys CockroachDB on a Kubernetes cluster. You can use the Operator to manage the configuration of a running CockroachDB cluster, including:
OpenEBS Dynamic LocalPV improves the operations of CockroachDB on Kubernetes. When compared to native Kubernetes Local Persistent Volumes, OpenEBS LocalPV volumes have the following advantages:
CockroachDB is an inherently resilient database that does not benefit from the complexity and shared dependencies of shared storage and is a perfect fit for Container Attached Storage.
OpenEBS LocalPV automates Storage Devices, the tagging and filtering of these devices, and pooling and other configurations - dynamically, as needed by CockroachDB.
OpenEBS is a widely deployed storage layer - and workflows such as capacity management and compliance reporting are simple to manage from common open source tools such as Grafana. Also, MayaData integrates and supports such workflows as a part of support for OpenEBS.
Step by step solution guide explains the steps and important considerations for deploying CockroachDB on Kubernetes using Dynamically Provisioned OpenEBS Local Persistent Volumes.