How to Survive Managing Strimzi in an Enterprise
summary
Platform team builds a self-service topic/app registry on Kubernetes using Strimzi so teams self‑onboard, set schemas, and approve access; authentication uses a unique principal builder that embeds CA info in principals to enforce tenant isolation. Deployment is two clusters with replication, static public endpoints per broker, TLS client auth, and dedicated nodes for Kafka. Monitoring uses Prometheus + Kafka exporter and Cruise Control. Outcome: 565 production topics, ~1,800 dev topics, 350 apps, 16 brokers, 2,700 partitions, 10 TB storage, 1,100 consumer groups and large ops reduction.
AI-written summary · about
chapters (9)
- 0:00Managing Strimzi in enterprise
- 1:47Business event bus platform design
- 6:03Access control and operations challenges
- 9:59Self-service topic management
- 12:07Strimzi for Kubernetes and multi-tenancy
- 18:15Secure external endpoints in Strimzi
- 22:10Optimizing resource usage and monitoring
- 31:39Scaling the platform and future outlook
- 32:46Q&A
related talks
30mFrom Running to Operating: Real-World Strimzi in Production
32mStretching Strimzi: Exploring Multi-Cluster Kafka for High Availability
31mSimplifying Apache Kafka on Kubernetes With Strimzi
21mKeynote: Strimzi past, present and future
26mProduction Grade Kafka on K8s
19mStrimzi & OpenTelemetry: Building End-to-End Observability for Kafka on Kubernetes
04mProject Lightning Talk: Strimzi – What's New and What's Next
29mMastering Kafka Workload Balancing With Strimzi’s Cruise Control Integration