Skip to content
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.

Are you using Knative Eventing Kafka? #1055

Open
pierDipi opened this issue Jan 12, 2022 · 2 comments
Open

Are you using Knative Eventing Kafka? #1055

pierDipi opened this issue Jan 12, 2022 · 2 comments
Labels
community triage/accepted Issues which should be fixed (post-triage)

Comments

@pierDipi
Copy link
Member

Are you using Knative Eventing Kafka?

If you are using Knative Eventing Kafka, we would love to know!

Why?

Tracking usage in Open Source Software is hard, we have thousands of downloads but we don't who they are.

If you leave a comment on this issue we can better understand who our users are and deliver a better experience for you!

  • We'd like to give your organization the opportunity to collaborate more closely with contributors (if you want to)
  • We want to help promote your organization
  • We want to show off all the awesome stuff our users are doing

How you can help

Submit a comment in this issue to include the following information, which would then also get included in the ADOPTERS.md file and (if applicable) on the Knative homepage:

Organization/Company: 
Website: 
Country: 
Contact: (email or Twitter at least one please!)
Usage scenario: e.g. We use Knative Eventing Kafka for XYZ
Status: Development?/Production?
APIs used: Kafka Broker, KafkaSink, KafkaChannel, KafkaSource, etc
@pierDipi pierDipi pinned this issue Jan 12, 2022
@nikt-lsq
Copy link

Organization/Company: LSQ
Website: https://lsq.com/
Country: USA
Contact: ntzaprev@lsq,com
Usage scenario: We use Knative Eventing Kafka for all events generated in our platform - we transitioning the system to an event driven serverless architecture
Status: Development but soon in Production (End of January 2022)
APIs used: Kafka Broker, KafkaChannel, Ping Source

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 14, 2022
@pierDipi pierDipi added triage/accepted Issues which should be fixed (post-triage) and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 14, 2022
@knative-extensions knative-extensions deleted a comment from github-actions bot Apr 14, 2022
@ashrafguitoni
Copy link

Organization/Company: CogentLabs
Website: https://www.cogent.co.jp/en
Country: JP
Contact: ashraf-guitoni@cogent.co.jp
Usage scenario: Using eventing to trigger machine learning inference services via Kafka messages.
Status: In development/evaluation
APIs used: KafkaSource

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
community triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Development

No branches or pull requests

3 participants