Strimzi-kafka-operator

Strimzi is an operator that runs and manages Apache Kafka on Kubernetes and OpenShift, letting you deploy Kafka, Kafka Connect, Kafka MirrorMaker, and…

  • Databases
  • Infrastructure
  • Tools & Utilities
Strimzi is an operator that runs and manages Apache Kafka on Kubernetes and OpenShift, letting you deploy Kafka, Kafka Connect, Kafka MirrorMaker, and ZooKeeper or KRaft clusters as Kubernetes custom resources instead of by hand.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

63/100 Good

Maintained
100last commit 1 day ago
Popular
765,982 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
103 serious findings, 2 minor, CI, tests, OpenSSF Scorecard 7.6/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
5,982
Open issues
171
Last commit
2026-11-20
Latest release
1.3.1
License
Apache-2.0
Activity
steady

Checked today - source: GitHub (strimzi/strimzi-kafka-operator)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the operator with Helm Use Helm (a Kubernetes package manager) to install a specific Strimzi version, and set `replicas` if you want more than one operator copy. This installs the controller that creates and manages Kafka; without it, your `Kafka` custom resource is not processed. source
  • Match replication settings to brokers In the Kafka custom resource, set `replication.factor`, `offsets.topic.replication.factor`, and `min.insync.replicas` to fit the number of brokers you are deploying. If they are set for a 3-broker cluster when you only run one broker, Kafka can fail to create or update topics. source
  • Allow connectors to read ConfigMaps If Kafka Connect should load configuration from a ConfigMap, create the Role shown in the docs that allows `get` on that specific ConfigMap. Without this permission, connector pods may start but fail to load the connector settings. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I expose Kafka to clients outside the Kubernetes cluster?

Strimzi can expose Kafka using NodePort, load balancer, Ingress, or OpenShift Routes. These endpoints can be secured with TLS.

Do I need separate Strimzi operators to manage Kafka topics and users?

The Topic Operator handles topic creation, updates, and deletion. The User Operator manages Kafka users and their authentication credentials.

Can I produce and consume Kafka messages over HTTP?

The HTTP Bridge provides a RESTful interface for producing and consuming messages.

Do I need to change custom password length settings when using Strimzi 0.33 or later?

From Strimzi 0.33, the default password length in the User Operator is 32 characters. If your configuration uses a shorter password length, you need to update it.

How can Strimzi assist with Kubernetes pod evictions?

If you are running the Cluster Operator, you can also use the Drain Cleaner to assist with pod evictions.

Answers sourced from strimzi.io, strimzi.io, strimzi.io

Community

Collected 48 days ago - public community threads