11-16, 12:00–12:30 (UTC), The Theater
Running geo-distributed clusters on Kubernetes presents no shortage of challenges: it complicates networking and service discovery; it mandates the use of stateful sets and persistent volumes; and it requires cleverness to navigate node pools and firewalls. Here's what we learned along the way.
When the engineers at Cockroach Labs started development on a global Database as a Service (DBaaS), they weren’t sure if Kubernetes would be the right choice for the underlying orchestration system. They wanted to harness Kubernetes’s powerful orchestration capabilities, but building a system to run geo-distributed Cockroach clusters on Kubernetes presents unique challenges: First, the clusters must run across multiple regions, complicating networking and service discovery. Second, the clusters must store data, requiring the use of stateful sets and persistent volumes. Third, the system must programmatically create Kubernetes clusters on AWS and GKE, which have different APIs for node pools and firewalls. In this presentation, they share their experience of overcoming these challenges to build a global DBaaS.
Pete is a software engineer at Cockroach Labs.
Josh spent his college years programming robots to play soccer in the RoboCup SPL league. There, he learned to love when very complicated computer systems break. This passion for broken computers led him to take an SRE job at Google working on source control systems. Six months ago he moved to Cockroach Labs to work on a DBaaS. Josh enjoyed Borg while at Google and has since spent many long hours puzzling over the strange land of Kubernetes. Josh can often be found roaming the Cockroach Labs NYC office yelling about things like strange node pool API semantics much to the confusion of his coworkers who don’t work on Kubernetes.