https://github.com/optum/kafka-topic-channel

kafka based knative channel implementation without kafka admin rights
https://github.com/optum/kafka-topic-channel

kafka knative knative-eventing

Last synced: 6 months ago
JSON representation

kafka based knative channel implementation without kafka admin rights

• Host: GitHub
• URL: https://github.com/optum/kafka-topic-channel
• Owner: Optum
• License: apache-2.0
• Created: 2021-06-03T18:49:45.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2024-03-06T20:18:20.000Z (over 1 year ago)
• Last Synced: 2025-04-14T15:22:04.036Z (6 months ago)
• Topics: kafka, knative, knative-eventing
• Language: Go
• Homepage:
• Size: 8.36 MB
• Stars: 7
• Watchers: 3
• Forks: 3
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

          
# Kafka Topic Channel

[![Go Report Card](https://goreportcard.com/badge/github.com/optum/faas-swagger)](https://goreportcard.com/badge/github.com/optum/kafka-topic-channel)

[![go.dev reference](https://img.shields.io/badge/go.dev-reference-007d9c?logo=go&logoColor=white)](https://pkg.go.dev/github.com/optum/kafka-topic-channel)

[![LICENSE](https://img.shields.io/github/license/knative/serving.svg)](https://github.com/optum/kafka-topic-channel/blob/master/LICENSE)

Kafka Topic Channel is a knative channel class based on kafka topic

### Why ?

There are already knative maintained channels like kafka consolidated, kafka distributed, inmemory channel, why new channel? The answer is 

Knative eventing primitives like broker, trigger and subscription are great for event processing, but they rely on the underlying channel. The existing kafka based channels needs kafka admin rights and requires the knative operator to maintain the kafka cluster or find a managed kafka cluster with admin rights. As a knative operator its challenging to maintain another big solution like kafka. If you are in the same boat, this kafka channel solution might work for you.

This implementation,

* Creates a knative channel based on the Kafka Topic information in any namespace.

* Kafka connection information is identical to kafka source

* Other knative primitives like broker, trigger and subscription works as is on this channel

* Each kafka topic channel resource would create a separate dispatcher/channel pod

* Bring your own kafka topic, get a knative channel

### Installation

Prereq for using this channel is knative eventing with broker. 

Once you have knative eventing in your cluster, install knative-topic-channel.

```shell

kubectl apply -f config/release/release.yaml

```

### Usage

Please take a look at the [samples](./samples) on how to use this channel.

### Contributing to the Project

The team is open to contributions to our project. For more details, see our [Contribution Guide.](./CONTRIBUTING.md)