Stretching Strimzi: Exploring Multi-Cluster Kafka for High Availability
summary
Proposal claims Strimzi can run Kafka brokers and controllers across multiple Kubernetes clusters while managing a single Kafka CR; it uses Kubernetes MCS with per-cluster IDs (KEP 2149), network fabrics like Submariner or Cilium, and a central operator that pushes node-pool resources to remote clusters annotated with strimzi.io/enable-stretch-cluster:true. The team publishes a working POC across 3 clusters on GitHub, configures advertised listeners and TLS SANs for multi‑cluster DNS, and reports the prototype functioning but still under active revision.
AI-written summary · about
chapters (16)
- 0:00Strimzi stretch clusters intro
- 1:26Multi-cluster Kafka need
- 3:56Zero downtime migration
- 7:47Multi-cloud hybrid benefits
- 9:13Kubernetes for Kafka ops
- 10:16Stretch clusters tech
- 13:53Submariner Cilium networking
- 15:18Strimzi operator deploy
- 16:46Kafka node pools across clusters
- 18:30Broker controller config
- 19:37Cross-cluster TLS security
- 21:00Live demo setup
- 23:49Remote cluster resources
- 24:50Broker controller quorum
- 25:56Stretch clusters status
- 27:19Q&A maintenance network
related talks
31mSimplifying Apache Kafka on Kubernetes With Strimzi
34mHow to Survive Managing Strimzi in an Enterprise
42mTransition to Apache Kafka on Kubernetes With Strimzi
42mPartial Multi-Tenancy on Kafka Using Strimzi at LittleHorse
30mFrom Running to Operating: Real-World Strimzi in Production
26mReleased From the Cage: Apache Kafka Without Its ZooKeeper
04mProject Lightning Talk: Strimzi – What's New and What's Next
29mMastering Kafka Workload Balancing With Strimzi’s Cruise Control Integration