kafka not secured apicurio registry sink Kafka Not Secured with Apicurio Registry secured with Keycloak Sink

Provided by: "Apache Software Foundation"

Support Level for this Kamelet is: "Stable"

Send data to Kafka topics on an insecure broker with Apicurio Registry secured with Keycloak.

The Kamelet is able to understand the following headers to be set:

  • key / ce-key: as message key

  • partition-key / ce-partitionkey: as message partition key

Both the headers are optional.

Three headers, if specified, will be deduplicated with different names, kafka.key will be duplicated into kafka.KEY, kafka.topic into kafka.TOPIC and kafka.override_topic into kafka.OVERRIDE_TOPIC

Configuration Options

The following table summarizes the configuration options available for the kafka-not-secured-apicurio-registry-sink Kamelet:

Property Name Description Type Default Example

apicurioAuthClientId

Apicurio Registry Auth Client ID

Required The Client ID in Keycloak instance securing the Apicurio Registry.

string

apicurioAuthClientSecret

Apicurio Registry Auth Client Secret

Required The Client Secret in Keycloak instance securing the Apicurio Registry.

string

apicurioAuthPassword

Apicurio Registry Auth Password

Required The Password in Keycloak instance securing the Apicurio Registry.

string

apicurioAuthRealm

Apicurio Registry Auth Realm

Required The Realm in Keycloak instance securing the Apicurio Registry.

string

apicurioAuthServiceUrl

Apicurio Registry Auth Service URL

Required The URL for Keycloak instance securing the Apicurio Registry.

string

http://my-keycloak.com:8080/

apicurioAuthUsername

Apicurio Registry Auth Username

Required The Username in Keycloak instance securing the Apicurio Registry.

string

apicurioRegistryUrl

Apicurio Registry URL

Required The Apicurio Schema Registry URL.

string

bootstrapServers

Bootstrap Servers

Required Comma separated list of Kafka Broker URLs.

string

topic

Topic Names

Required Comma separated list of Kafka topic names.

string

avroDatumProvider

Avro Datum Provider

How to write data with Avro.

string

io.apicurio.registry.serde.avro.ReflectAvroDatumProvider

valueSerializer

Value Serializer

Serliazer class for value that implements the Serializer interface.

string

io.apicurio.registry.serde.avro.AvroKafkaSerializer

Dependencies

At runtime, the kafka-not-secured-apicurio-registry-sink Kamelet relies upon the presence of the following dependencies:

  • camel:core

  • camel:kamelet

  • camel:kafka

  • mvn:io.apicurio:apicurio-registry-serdes-avro-serde:2.4.14.Final

Camel JBang usage

Prerequisites

  • You’ve installed JBang.

  • You have executed the following command:

jbang app install camel@apache/camel

Supposing you have a file named route.yaml with this content:

- route:
    from:
      uri: "kamelet:timer-source"
      parameters:
        period: 10000
        message: 'test'
      steps:
        - to:
            uri: "kamelet:log-sink"

You can now run it directly through the following command

camel run route.yaml

Camel K Environment Usage

This section describes how you can use the kafka-not-secured-apicurio-registry-sink.

Knative sink

You can use the kafka-not-secured-apicurio-registry-sink Kamelet as a Knative sink by binding it to a Knative object.

kafka-not-secured-apicurio-registry-sink-pipe.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
  name: kafka-not-secured-apicurio-registry-sink-pipe
spec:
  source:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: kafka-not-secured-apicurio-registry-sink
    properties:
      apicurioAuthClientId: The Apicurio Registry Auth Client ID
      apicurioAuthClientSecret: The Apicurio Registry Auth Client Secret
      apicurioAuthPassword: The Apicurio Registry Auth Password
      apicurioAuthRealm: The Apicurio Registry Auth Realm
      apicurioAuthServiceUrl: http://my-keycloak.com:8080/
      apicurioAuthUsername: The Apicurio Registry Auth Username
      apicurioRegistryUrl: The Apicurio Registry URL
      bootstrapServers: The Bootstrap Servers
      topic: The Topic Names

Prerequisite

You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the kafka-not-secured-apicurio-registry-sink-pipe.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command:

    kubectl apply -f kafka-not-secured-apicurio-registry-sink-pipe.yaml

Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind channel:mychannel -p "sink.apicurioAuthClientId=The Apicurio Registry Auth Client ID" -p "sink.apicurioAuthClientSecret=The Apicurio Registry Auth Client Secret" -p "sink.apicurioAuthPassword=The Apicurio Registry Auth Password" -p "sink.apicurioAuthRealm=The Apicurio Registry Auth Realm" -p "sink.apicurioAuthServiceUrl=\http://my-keycloak.com:8080/" -p "sink.apicurioAuthUsername=The Apicurio Registry Auth Username" -p "sink.apicurioRegistryUrl=The Apicurio Registry URL" -p "sink.bootstrapServers=The Bootstrap Servers" -p "sink.topic=The Topic Names" kafka-not-secured-apicurio-registry-sink

This command creates the Kamelet Pipe in the current namespace on the cluster.

Kafka sink

You can use the kafka-not-secured-apicurio-registry-sink Kamelet as a Kafka sink by binding it to a Kafka topic.

kafka-not-secured-apicurio-registry-sink-pipe.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
  name: kafka-not-secured-apicurio-registry-sink-pipe
spec:
  source:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: kafka-not-secured-apicurio-registry-sink
    properties:
      apicurioAuthClientId: The Apicurio Registry Auth Client ID
      apicurioAuthClientSecret: The Apicurio Registry Auth Client Secret
      apicurioAuthPassword: The Apicurio Registry Auth Password
      apicurioAuthRealm: The Apicurio Registry Auth Realm
      apicurioAuthServiceUrl: http://my-keycloak.com:8080/
      apicurioAuthUsername: The Apicurio Registry Auth Username
      apicurioRegistryUrl: The Apicurio Registry URL
      bootstrapServers: The Bootstrap Servers
      topic: The Topic Names

Prerequisites

  • You’ve installed Strimzi.

  • You’ve created a topic named my-topic in the current namespace.

  • You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the kafka-not-secured-apicurio-registry-sink-pipe.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command:

    kubectl apply -f kafka-not-secured-apicurio-registry-sink-pipe.yaml

Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind kafka.strimzi.io/v1beta1:KafkaTopic:my-topic -p "sink.apicurioAuthClientId=The Apicurio Registry Auth Client ID" -p "sink.apicurioAuthClientSecret=The Apicurio Registry Auth Client Secret" -p "sink.apicurioAuthPassword=The Apicurio Registry Auth Password" -p "sink.apicurioAuthRealm=The Apicurio Registry Auth Realm" -p "sink.apicurioAuthServiceUrl=\http://my-keycloak.com:8080/" -p "sink.apicurioAuthUsername=The Apicurio Registry Auth Username" -p "sink.apicurioRegistryUrl=The Apicurio Registry URL" -p "sink.bootstrapServers=The Bootstrap Servers" -p "sink.topic=The Topic Names" kafka-not-secured-apicurio-registry-sink

This command creates the Kamelet Pipe in the current namespace on the cluster.

Kamelet source file

https://github.com/apache/camel-kamelets/blob/main/kamelets/kafka-not-secured-apicurio-registry-sink.kamelet.yaml

Back to top