4.6. Knative broker implementation for Apache Kafka

Procedure

1. Create a Kafka-based broker as a YAML file:

   apiVersion: eventing.knative.dev/v1
   kind: Broker
   metadata:
     annotations:
       eventing.knative.dev/broker.class: Kafka 

   1

   
     name: example-kafka-broker
   spec:
     config:
       apiVersion: v1
       kind: ConfigMap
       name: kafka-broker-config 

   2

   
       namespace: knative-eventing

   1

   The broker class. If not specified, brokers use the default class as configured by cluster administrators. To use the Kafka broker, this value must be Kafka.

   2

   The default config map for Knative brokers for Apache Kafka. This config map is created when the Kafka broker functionality is enabled on the cluster by a cluster administrator.

2. Apply the Kafka-based broker YAML file:

   $ oc apply -f <filename>

Procedure

1. Create a Kafka-based broker as a YAML file:

   apiVersion: eventing.knative.dev/v1
   kind: Broker
   metadata:
     annotations:
       eventing.knative.dev/broker.class: Kafka 

   1

   
       kafka.eventing.knative.dev/external.topic: <topic_name> 

   2

   
   ...

   1

   The broker class. If not specified, brokers use the default class as configured by cluster administrators. To use the Kafka broker, this value must be Kafka.

   2

   The name of the Kafka topic that you want to use.

2. Apply the Kafka-based broker YAML file:

   $ oc apply -f <filename>

Procedure

1. Create an Apache Kafka-based broker by using a YAML file:

   apiVersion: eventing.knative.dev/v1
   kind: Broker
   metadata:
     annotations:
       eventing.knative.dev/broker.class: KafkaNamespaced 

   1

   
     name: default
     namespace: my-namespace 

   2

   
   spec:
     config:
       apiVersion: v1
       kind: ConfigMap
       name: my-config 

   3

   
   ...

   1

   To use the Apache Kafka broker with isolated data planes, the broker class value must be KafkaNamespaced.

   2 3

   The referenced ConfigMap object my-config must be in the same namespace as the Broker object, in this case my-namespace.

2. Apply the Apache Kafka-based broker YAML file:

   $ oc apply -f <filename>

Procedure

1. Create the certificate files as a secret in the knative-eventing namespace:

   $ oc create secret -n knative-eventing generic <secret_name> \
     --from-literal=protocol=SSL \
     --from-file=ca.crt=caroot.pem \
     --from-file=user.crt=certificate.pem \
     --from-file=user.key=key.pem

   重要

   Use the key names ca.crt, user.crt, and user.key. Do not change them.

2. Edit the KnativeKafka CR and add a reference to your secret in the broker spec:

   apiVersion: operator.serverless.openshift.io/v1alpha1
   kind: KnativeKafka
   metadata:
     namespace: knative-eventing
     name: knative-kafka
   spec:
     broker:
       enabled: true
       defaultConfig:
         authSecretName: <secret_name>
   ...

Procedure

1. Create the certificate files as a secret in the knative-eventing namespace:

   $ oc create secret -n knative-eventing generic <secret_name> \
     --from-literal=protocol=SASL_SSL \
     --from-literal=sasl.mechanism=<sasl_mechanism> \
     --from-file=ca.crt=caroot.pem \
     --from-literal=password="SecretPassword" \
     --from-literal=user="my-sasl-user"

   • Use the key names protocol, sasl.mechanism, ca.crt, password, and user. Do not change them.

     注記

     The ca.crt key is optional if the Kafka cluster uses a certificate signed by a public CA whose certificate is already in the system truststore.

2. Edit the KnativeKafka CR and add a reference to your secret in the broker spec:

   apiVersion: operator.serverless.openshift.io/v1alpha1
   kind: KnativeKafka
   metadata:
     namespace: knative-eventing
     name: knative-kafka
   spec:
     broker:
       enabled: true
       defaultConfig:
         authSecretName: <secret_name>
   ...