Transition to Apache Kafka on Kubernetes With Strimzi
summary
Maersk migrates from Confluent Platform and Confluent Cloud to self‑managed Apache Kafka on Kubernetes using Strimzi, claiming a running fleet of 63 clusters (including edge terminals), servicing 210+ tenants with 250M messages/day, 13k+ topics and 22k+ schemas. Tooling includes Strimzi, MirrorMaker2, a Confluent Community schema registry, Grafana/Prometheus + GoAlert, HashiCorp Vault, GitOps with Flux and Kustomize and Go APIs, plus an open source Routina manager for secure topic message browsing and a schema compatibility UI, and the platform reports 99.9% SLA.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:52Company logistics
- 3:16Past architecture
- 7:19Reasons for Strimzi
- 10:33Self-managed clusters
- 18:25Developer tooling
- 27:40Strimzi contributions
- 29:28Future Kafka plans
- 33:01Stream processing
- 34:49Q&A
related talks
31mSimplifying Apache Kafka on Kubernetes With Strimzi
30mFrom Running to Operating: Real-World Strimzi in Production
44mTaming Apache Kafka Using GitOps
32mStretching Strimzi: Exploring Multi-Cluster Kafka for High Availability
04mProject Lightning Talk: Strimzi – What's New and What's Next
21mKeynote: Strimzi past, present and future
19mStrimzi & OpenTelemetry: Building End-to-End Observability for Kafka on Kubernetes
50mRunning Apache Kafka on Kubernetes and OpenShift