Strimzi
Strimzi is a CNCF Incubating project that provides Kubernetes operators for deploying and managing Apache Kafka clusters. It simplifies Kafka operations through Custom Resources, automated TLS encryption, and integrations with Kafka Connect, MirrorMaker 2.0, and Cruise Control.
Strimzi is the leading Kubernetes operator for Apache Kafka, providing a cloud-native way to deploy, manage, and operate Kafka clusters. As a CNCF Incubating project with 5,700+ GitHub stars and 300+ contributors, it has become the de facto standard for running Kafka on Kubernetes.
Key features
Kubernetes-native management
- Deploy and manage Kafka using kubectl and GitOps workflows
- Custom Resources for clusters, topics, users, and connectors
- Operator-based lifecycle management with automated rolling updates
Security by default
- TLS encryption for all internal and external communication
- SCRAM-SHA and OAuth 2.0 authentication support
- Automated certificate management and renewal
- Fine-grained authorization with ACLs
High availability
- Rack awareness across availability zones
- Support for Kubernetes taints and tolerations for dedicated nodes
- Automated pod disruption handling with Drain Cleaner
Data integration
- Kafka Connect for integrating with external systems
- MirrorMaker 2.0 for cross-cluster and cross-region replication
- Kafka Bridge providing REST API for HTTP clients
- Cruise Control integration for automated partition rebalancing
Deployment options
Development
- Minikube (4GB+ RAM)
- Kubernetes Kind
- Docker Desktop with Kubernetes
Production
- Any Kubernetes distribution (cloud or on-premise)
- OpenShift
- Rack-aware configurations for multi-AZ deployments
- External access via NodePort, LoadBalancer, Ingress, or OpenShift Routes
Integrations
- Prometheus: Metrics export for monitoring
- Grafana: Dashboards for Kafka metrics
- OAuth 2.0: Authentication providers (Keycloak, etc.)
- Kubernetes: Native operators and CRDs
Limitations
- Requires Kubernetes — cannot deploy on bare metal or VMs without K8s
- Inherits Apache Kafka's operational complexity (partition management, broker tuning, consumer lag)
- No built-in GUI for cluster management — relies on kubectl and YAML manifests (or third-party tools like Conduktor)
- ZooKeeper is still required for some configurations (KRaft support is newer)
- Limited to Kafka ecosystem — does not support alternative streaming platforms
Complements
Strimzi
RabbitMQStrimzi (Kafka) and RabbitMQ serve different messaging patterns. Strimzi excels at high-throughput, durable event streaming with replay capabilities, while RabbitMQ is optimized for complex routing and RPC patterns. Many organizations use both: RabbitMQ for command/control messaging and Strimzi-managed Kafka for event streaming and data pipelines.
Strimzi
NATSStrimzi-managed Kafka and NATS serve complementary use cases in event-driven architectures. Strimzi provides durable, high-throughput event streaming with long-term retention, while NATS excels at lightweight, low-latency messaging and pub/sub. Organizations often use NATS for real-time control plane communication and Strimzi/Kafka for data plane event streaming.
Strimzi
Apache FlinkStrimzi (Kafka on Kubernetes) and Apache Flink are often used together in stream processing architectures. Strimzi provides the event streaming backbone via Kafka, while Flink provides stateful stream processing capabilities. Flink can consume from and produce to Kafka topics managed by Strimzi.
Similar to Strimzi
