[](https://strimzi.io/)

Run Apache Kafka on Kubernetes and OpenShift

https://artifacthub.io/badge/repository/strimzi-kafka-operator" rel="noopener nofollow" target="_blank">

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](development-docs/DEV_GUIDE.md) 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](development-docs/TESTING.md).
The [release checklist](development-docs/RELEASE.md) 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

If you want to get in touch with us first before contributing, you can use:

• #strimzi channel on CNCF Slack
• Strimzi Dev mailing list

License

Strimzi is licensed under the [Apache License](./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.
To verify the container, you can run the following command:

shell
cosign verify --certificate-identity-regexp='https://github.com/strimzi/.*' \
    --certificate-oidc-issuer='https://token.actions.githubusercontent.com' \
    quay.io/strimzi/operator:latest

In case you want to verify containers of older version of Strimzi than 0.49.0, then use our public key:

-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAET3OleLR7h0JqatY2KkECXhA9ZAkC
TRnbE23Wb5AzJPnpevvQ1QUEQQ5h/I4GobB7/jkGfqYkt6Ct5WOU2cc6HQ==
-----END PUBLIC KEY-----

And use it to verify the signature:

shell
cosign verify --key strimzi.pub quay.io/strimzi/operator:latest --insecure-ignore-tlog=true

Software Bill of Materials (SBOM)

From the 0.38.0 release, Strimzi publishes the software bill of materials (SBOM) of our containers.
The SBOMs are published as an archive with SPDX-JSON and Syft-Table formats signed using cosign.
For releases, they are also pushed into the container registry.

Strimzi uses keyless signing since 0.49.0 release.
To verify the SBOM signatures, you can run the following command:

shell
cosign verify-blob --bundle .bundle \
    --certificate-identity-regexp='https://github.com/strimzi/.*' \
    --certificate-oidc-issuer='https://token.actions.githubusercontent.com' \

In case you want to verify SBOM signatures of older version of Strimzi than 0.49.0, then use our public key:

-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAET3OleLR7h0JqatY2KkECXhA9ZAkC
TRnbE23Wb5AzJPnpevvQ1QUEQQ5h/I4GobB7/jkGfqYkt6Ct5WOU2cc6HQ==
-----END PUBLIC KEY-----

You can use it to verify the signature of the SBOM files with the following command:

shell
cosign verify-blob --key cosign.pub --bundle .bundle --insecure-ignore-tlog=true

---

Strimzi is a Cloud Native Computing Foundation incubating project.


[strimzi]: https://strimzi.io "Strimzi"
[kafka]: https://kafka.apache.org "Apache Kafka"
[k8s]: https://kubernetes.io/ "Kubernetes"
[os]: https://www.openshift.com/ "OpenShift"

Collapse