Apache License 2.0

项目介绍

strimzi/strimzi-kafka-operator 是一个托管在 GitHub 上的开源项目,主要使用 Java 编写,采用 Apache License 2.0 许可证,目前获得 6.0k 个 Star、1.6k 次 Fork。

仓库全名
strimzi/strimzi-kafka-operator
开源许可证
Apache License 2.0
Star 数
6.0k
Fork 数
1.6k
未关闭 Issue
165

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…

完整内容见 GitHub 原始 README 或本页 。

常见问题

strimzi-kafka-operator 用什么语言开发?

主要使用 Java 编写,采用 Apache License 2.0 许可证,目前有 6.0k 个 Star。

strimzi-kafka-operator 可以免费商用吗?

仓库采用 Apache License 2.0 许可证,可免费使用与修改,商业使用请遵守许可证条款(例如保留版权声明与许可声明)。

如何获取 strimzi-kafka-operator 的源码?

可以直接克隆仓库:git clone https://github.com/strimzi/strimzi-kafka-operator.git,默认分支为 main;安装与运行步骤见仓库 README。

strimzi-kafka-operator 最近还在维护吗?

仓库最近一次更新为 21 小时前,当前有 165 个未关闭 Issue;Star 数为 6.0k,可作为社区活跃度的参考。

关于

GitHub 原始描述(英文)

Apache Kafka® running on Kubernetes

描述取自 GitHub 官方 API,保持仓库作者书写的原文。

简要分析

热度分
9203
价值分
4054
活跃状态
活跃

语言占比

1C Enterprise
Awk
Dockerfile
Java
Makefile
Mustache
Shell

Release

README

Strimzi

Run Apache Kafka on Kubernetes and OpenShift

OpenSSF Best Practices OpenSSF Scorecard OSPS Baseline Build Status GitHub release License Twitter Follow Artifact Hub FOSSA Status Known Vulnerabilities

Strimzi provides a way to run an Apache Kafka® cluster on Kubernetes or OpenShift in various deployment configurations. See our website 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.

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 Community Meetings

You can join our regular community meetings:

Resources:

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.

This is my commit message

Signed-off-by: John Doe <[email protected]>

Git has a -s option to append this automatically:

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:

git commit --amend -s

Getting help with your contributions

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

License

Strimzi is licensed under the Apache License, Version 2.0

Community Testing

Linux on IBM Z (s390x)

Jenkins

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:

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:

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:

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

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:

cosign verify-blob --key cosign.pub --bundle <SBOM-file>.bundle --insecure-ignore-tlog=true <SBOM-file>

Strimzi is a Cloud Native Computing Foundation incubating project.

CNCF ><

评论

暂无评论