strimzi /strimzi-kafka-operator
Apache Kafka® running on Kubernetes
★ 5,981⑂ 1,573👁 95⑃ 7,547● 3,198▤ 184
+2
Daily
5,981
stars
1,573
forks
95
watchers
7,547
prs
3,198
issues
184
releases
README
Run Apache Kafka on Kubernetes and OpenShift Strimzi provides a way to run an [Apache Kafka®][kafka] cluster on [Kubernetes][k8s] or [OpenShift][os] in various deployment configurations. See our [website][strimzi] for more details about the project. Quick Starts To get up and running quickly, check our Quick Start for Minikube, OKD (OpenShift Origin) and Kubernetes Kind. Documentation Documentation for the current _main_ branch as well as all releases can be found on our [website][strimzi]. Roadmap The roadmap of the Strimzi Operator project is maintained as GitHub Project. Getting help If you encounter any issues while using Strimzi, you can get help using: - strimzi channel on CNCF Slack - Strimzi Users mailing list - GitHub Discussions Strimzi Community Meetings You can join our regular community meetings: Thursday 9:00 AM UTC (every 4 weeks) - convert to your timezone Thursday 4:00 PM UTC (every 4 weeks, offset by 2 weeks from above meeting) - convert to your timezone Resources: Meeting minutes, agenda and Zoom link Recordings Calendar (Subscribe to the calendar) Contributing You can contribute by: - Raising issues you find while using Strimzi - Fixing issues by opening Pull Requests - Improving Strimzi documentation - Talking about Strimzi All bugs, tasks or enhancements are tracked as GitHub issues. Issues which might be a good start for new contributors are marked with "good-start" label. The development guide describes how to quickly get set up to build Strimzi from source. Before submitting a patch, make sure you understand how to test your changes by reading the Test guide. The release checklist describes the steps needed for a new version release. The documentation contributor guide describes how to contribute to Strimzi documentation. Developer Certificate of Origin The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. All commits must be signed off by adding a Signed-off-by line to the commit message. shell This is my commit message Signed-off-by: John Doe Git has a -s option to append this automatically: shell git commit -s -m 'This is my commit message' If you have already made a commit and forgot to include the sign-off, you can amend your last commit: shell git commit --amend -s Getting help with your contributions If you want to get in touch with us first before contributing, you can use: - strimzi-dev channel on CNCF Slack - Strimzi Dev mailing list License Strimzi is licensed under the Apache License, Version 2.0 Community Testing Linux on IBM Z (s390x) _Note: This badge represents a community-led initiative and is not officially endorsed by the Strimzi project maintainers._ Container signatures From the 0.38.0 release, Strimzi containers are signed using the cosign tool. Strimzi uses keyless signing since 0.49.0 release
Top issues
#3697[Enhancement] Stretch Kafka cluster over multiple Kubernetes clusters32 comments · 2020-09-23#3601[Enhancement] Start using CC self heal features31 comments · 2020-09-03#2976[Enhancement] Possibility to configure more containers in a Pod (sidecars, init containers)26 comments · 2020-05-07#11375Python >= 3.13 clients fail to connect with self-signed TLS certs due to VERIFY_X509_STRICT24 comments · 2025-04-22#3984[Enhancement] Advertise pod IPs in listener23 comments · 2020-11-19#11634Create alerting mechanism for stuck reconciliations20 comments · 2025-07-10#11279[Bug]: Strimzi restart pod with pvc in FileSystemResizePending state before it can be resized online without restart20 comments · 2025-03-20#9429[KRaft] Scaling of controller nodes20 comments · 2023-12-04
Discussions
#13358KRaft broker startup probe alternative to JVM check3 comments · 2026-11-05#13298Metrics reporter allowlist is re-applied as a dynamic broker config on every reconciliation, flooding logs (Strimzi 1.0.1)1 comments · 2026-10-22#13237Support for granular & parallel updates3 comments · 2026-10-09#13219Ability to turn of ScramShaCredentialsCache feature in UserOperator1 comments · 2026-10-05#13214Kafka MirrorMaker2 cannot replicate messages when adding a third Kafka cluster (Strimzi 0.35.1 / Kafka 3.4.0)2 comments · 2026-10-02#13125[Bug]: unexpected container restart2 comments · 2026-09-04#13120Ability to exclude Cruise Control1 comments · 2026-09-02#13117[KRaft] Stale ControllerRegistrationRecord for removed controller ID 8 blocks metadata.version 3.9-IV0 and is invisible to Strimzi status2 comments · 2026-09-01
Latest release
1.3.1 1.3.1 2026-11-04⚠️ Important: Strimzi 1.3.1 supports only Kubernetes 1.32 and newer. Kubernetes 1.30 and 1.31 are not supported anymore. ⚠️ ⚠️ ⚠️ Important: From Strimzi 1.0.0, the only supported version of CRD API is v1. The older v1beta2, v1beta1, and v1alpha1 APIs are no longer supported. Before upgrading to Strimzi 1.0.0 and above, make sure to convert all custom resources and upgrade the CRDs. ---- Main Changes Since 1.3.0 The most important new features are: Added support for Kafka 4.3.2 Fix concurrency issues after Vert.x removal Dependency updates (Cruise Control, Vert.x, Netty,