Recommended Free Tools
The Linux Foundation’s on-demand webinar, recorded April 8, 2021, describes a CockroachDB deployment spanning three Kubernetes clusters and focuses on the security and networking challenges of a multi-cluster application. Its listing names multi-cluster secrets management and Skupper, but does not publish the demo’s topology or configuration. View the webinar listing.
What the webinar says it demonstrates
The session was sponsored by Cockroach Labs. The listing names Jim Walker, VP of Product Marketing, and Keith McClellan, Director of Partner Solutions Engineering, both of Cockroach Labs, as speakers. It says the demonstration covers CockroachDB on Kubernetes across three clusters, with attention to security, networking, a candidate reference architecture, multi-cluster secrets management, and Skupper as a cross-domain networking solution.
The listing frames the central challenge this way: “Running anything multi-cluster in Kubernetes presents a range of challenges and in this session, we will talk through a few of the major issues with security and networking.” This is the listing’s wording, not a quotation attributed to either speaker.
As an Amazon Associate I earn from qualifying purchases.
Two different kinds of distribution are involved
A multi-cluster design can distribute the database itself, the application services that use it, or both. Those are related architectural concerns, but they are not the same mechanism.
Database topology
Cockroach Labs’ current product information describes CockroachDB as deployable across Kubernetes clusters as one logical database. That is the vendor’s current product positioning; it does not establish the exact topology shown in the 2021 webinar. CockroachDB on Kubernetes.
#1 Best Overall
Application networking
Skupper’s current documentation describes an application network that lets services communicate across sites. It forwards service traffic between connected sites; it is not described as implementing CockroachDB’s database replication. Skupper documentation.
Keeping these layers distinct helps clarify the architecture question: database replication and placement determine how the database is distributed, while an application network addresses how services reach one another across cluster boundaries.
Free tools Windows power users keep installed
One-click scans. No signup required.
What current Skupper documentation explains
Skupper’s current connectivity documentation describes connecting services across Kubernetes clusters without exposing them publicly or setting up a VPN. It says site-to-site communication uses mutual TLS authentication and encryption. This explains the general networking concept behind the webinar listing’s reference to Skupper, but does not verify the Skupper version, manifests, control plane, or security policy used in the April 2021 session. Skupper connectivity documentation.
What to check when evaluating a multi-cluster design
- Database goal: Decide whether the requirement is one logical CockroachDB database distributed across clusters, an application whose services span clusters, or both.
- Network boundary: Identify how services cross cluster boundaries, whether they are exposed publicly, and how cross-site communication is authenticated and encrypted. Skupper documents mutual TLS for its current site communication.
- Secret handling: Treat multi-cluster secrets management as a separate design question. The webinar listing names it as a topic but does not identify a secret-distribution mechanism or its configuration.
- Guide scope: Check whether CockroachDB deployment instructions cover one Kubernetes cluster or a geographically distributed deployment. The CockroachDB Kubernetes repository distinguishes basic single-cluster examples from separate guidance for geographically distributed deployments. CockroachDB Kubernetes repository.
What the public information does not establish
The event listing does not disclose the demo’s precise topology, secret-distribution mechanism, CockroachDB version, or Skupper version. Those details should not be inferred from current product documentation. The cited material also provides no measured latency, throughput, uptime, cost, or operational-savings results, so the webinar description cannot support a performance or cost conclusion.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
