Why We Run CockroachDB Dedicated on Kubernetes image

Why We Run CockroachDB Dedicated on Kubernetes

Published Thursday, Oct 31, 2019

Watch the webinar

When we started development on CockroachDB Dedicated, we weren’t sure if Kubernetes would be the right choice for the underlying orchestration system. 

We wanted to harness Kubernetes’s powerful orchestration capabilities, but building a system to run geo-distributed Cockroach clusters on Kubernetes presented unique challenges: 
  1. The clusters must run across multiple regions, which complicates networking and service discovery. 
  2. The clusters must store data, which requires the use of stateful sets and persistent volumes -- something that is notoriously tricky with Kubernetes.
  3. The system must programmatically create Kubernetes clusters on AWS and GKE, so it must navigate unique APIs for node pools and firewalls. 
In this candid technical conversation, Josh Imhoff, the Technical Lead of the Site Reliability team, will share his team’s experience of overcoming these challenges to build CockroachDB Dedicated.


Josh Imhoff
Josh Imhoff
Technical Lead of SRE Team
Amruta Ranade
Amruta Ranade
Technical Writer

Additional Resources

Learn how to use CockroachDB
Read the docs
Need help? Get answers on the CockroachDB forum
Ask on the forum
What are you building with CockroachDB?
Share your project