Kafka Not Secured Sink
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Send data to Kafka topics on an insecure broker.
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-sink Kamelet:
Dependencies
At runtime, the kafka-not-secured-sink Kamelet relies upon the presence of the following dependencies:
-
camel:core
-
camel:kafka
-
mvn:org.apache.camel.kamelets:camel-kamelets-utils:4.0.4-SNAPSHOT
-
camel:kamelet
Camel JBang usage
Prerequisites
-
You’ve installed JBang.
-
You have executed the following command:
jbang app install camel@apache/camelSupposing 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.yamlCamel K Environment Usage
This section describes how you can use the kafka-not-secured-sink.
Knative sink
You can use the kafka-not-secured-sink Kamelet as a Knative sink by binding it to a Knative object.
apiVersion: camel.apache.org/v1
kind: KameletBinding
metadata:
name: kafka-not-secured-sink-binding
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-sink
properties:
bootstrapServers: The Bootstrap Servers
topic: The Topic NamesPrerequisite
You have Camel K installed on the cluster.
Procedure for using the cluster CLI
-
Save the
kafka-not-secured-sink-binding.yamlfile to your local drive, and then edit it as needed for your configuration. -
Run the sink by using the following command:
kubectl apply -f kafka-not-secured-sink-binding.yaml
Procedure for using the Kamel CLI
Configure and run the sink by using the following command:
kamel bind channel:mychannel -p "sink.bootstrapServers=The Bootstrap Servers" -p "sink.topic=The Topic Names" kafka-not-secured-sinkThis command creates the KameletBinding in the current namespace on the cluster.
Kafka sink
You can use the kafka-not-secured-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
apiVersion: camel.apache.org/v1
kind: KameletBinding
metadata:
name: kafka-not-secured-sink-binding
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-sink
properties:
bootstrapServers: The Bootstrap Servers
topic: The Topic NamesPrerequisites
-
You’ve installed Strimzi.
-
You’ve created a topic named
my-topicin the current namespace. -
You have Camel K installed on the cluster.
Procedure for using the cluster CLI
-
Save the
kafka-not-secured-sink-binding.yamlfile to your local drive, and then edit it as needed for your configuration. -
Run the sink by using the following command:
kubectl apply -f kafka-not-secured-sink-binding.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.bootstrapServers=The Bootstrap Servers" -p "sink.topic=The Topic Names" kafka-not-secured-sinkThis command creates the KameletBinding in the current namespace on the cluster.