We use analytics and cookies to understand site traffic. Information about your use of our site is shared with Google for that purpose. Learn more.
Apache Kafka Channel Example
You can install and configure the Apache Kafka CRD (
KafkaChannel) as the default channel configuration in Knative Eventing.
- Ensure that you meet the prerequisites listed in the Apache Kafka overview.
- A Kubernetes cluster with Knative Kafka Channel installed.
KafkaChannel channel CRD
Create a new object by configuring the YAML file as follows:
cat <<-EOF | kubectl apply -f - --- apiVersion: messaging.knative.dev/v1alpha1 kind: KafkaChannel metadata: name: my-kafka-channel spec: numPartitions: 3 replicationFactor: 1 EOF
Specifying the default channel configuration
To configure the usage of the
KafkaChannel CRD as the
default channel configuration,
default-ch-webhook ConfigMap as follows:
cat <<-EOF | kubectl apply -f - --- apiVersion: v1 kind: ConfigMap metadata: name: default-ch-webhook namespace: knative-eventing data: # Configuration for defaulting channels that do not specify CRD implementations. default-ch-config: | clusterDefault: apiVersion: messaging.knative.dev/v1alpha1 kind: KafkaChannel spec: numPartitions: 3 replicationFactor: 1 EOF
Creating an Apache Kafka channel using the default channel configuration
KafkaChannel is set as the default channel configuration, you can use the
channels.messaging.knative.dev CRD to create a new Apache Kafka channel, using the generic
cat <<-EOF | kubectl apply -f - --- apiVersion: messaging.knative.dev/v1beta1 kind: Channel metadata: name: testchannel-one EOF
Check Kafka for a
testchannel topic. With Strimzi this can be done by using the command:
kubectl -n kafka exec -it my-cluster-kafka-0 -- bin/kafka-topics.sh --zookeeper localhost:2181 --list
The result is:
... knative-messaging-kafka.default.testchannel-one ...
The Apache Kafka topic that is created by the channel implementation is prefixed with
knative-messaging-kafka. This indicates it is an Apache Kafka channel from Knative. It contains the name of the namespace,
default in this example, followed by the actual name of the channel.
Configuring the Knative broker for Apache Kafka channels
To setup a broker that will use the new default Kafka channels, you must inject a new default broker, using the command:
kubectl label namespace default knative-eventing-injection=enabled
This will give you two pods, such as:
default-broker-filter-64658fc79f-nf596 1/1 Running 0 15m default-broker-ingress-ff79755b6-vj9jt 1/1 Running 0 15m
Inside the Apache Kafka cluster you should see two new topics, such as:
... knative-messaging-kafka.default.default-kn2-ingress knative-messaging-kafka.default.default-kn2-trigger ...
Creating a service and trigger to use the Apache Kafka broker
To use the Apache Kafka based broker, let’s take a look at a simple demo. Use the
ApiServerSource to publish events to the broker as well as the
Trigger API, which then routes events to a Knative
ksvc, using the command:
kubectl apply -f 000-ksvc.yaml
Install a source that publishes to the default broker
kubectl apply -f 020-k8s-events.yaml
Create a trigger that routes the events to the
kubectl apply -f 030-trigger.yaml
Verifying your Apache Kafka channel and broker
Now that your Eventing cluster is configured for Apache Kafka, you can verify your configuration with the following options.
Receive events via Knative
Now you can see the events in the log of the
ksvc using the command:
kubectl logs --selector='serving.knative.dev/service=broker-kafka-display' -c user-container
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.