Kafka Not Secured Source
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Receive data from Kafka topics on an insecure broker.
Configuration Options
The following table summarizes the configuration options available for the kafka-not-secured-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
Bootstrap Servers |
Required Comma separated list of Kafka Broker URLs. |
string |
|||
Topic Names |
Required Comma separated list of Kafka topic names. |
string |
|||
Allow Manual Commit |
Whether to allow doing manual commits. |
boolean |
false |
||
Auto Commit Enable |
If true, periodically commit to ZooKeeper the offset of messages already fetched by the consumer. |
boolean |
true |
||
Auto Offset Reset |
What to do when there is no initial offset. There are 3 enums and the value can be one of latest, earliest, none. |
string |
latest |
||
Consumer Group |
A string that uniquely identifies the group of consumers to which this source belongs. |
string |
my-group-id |
||
Poll On Error Behavior |
What to do if kafka threw an exception while polling for new messages. There are 5 enums and the value can be one of DISCARD, ERROR_HANDLER, RECONNECT, RETRY, STOP. |
string |
ERROR_HANDLER |
Dependencies
At runtime, the kafka-not-secured-source
Kamelet relies upon the presence of the following dependencies:
-
camel:kafka
-
camel:kamelet
Usage
This section describes how you can use the kafka-not-secured-source
.
Knative source
You can use the kafka-not-secured-source
Kamelet as a Knative source by binding it to a Knative object.
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: kafka-not-secured-source-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: kafka-not-secured-source
properties:
bootstrapServers: The Bootstrap Servers
topic: The Topic Names
sink:
ref:
kind: Channel
apiVersion: messaging.knative.dev/v1
name: mychannel
Prerequisite
You have Camel K installed on the cluster.
Procedure for using the cluster CLI
-
Save the
kafka-not-secured-source-binding.yaml
file to your local drive, and then edit it as needed for your configuration. -
Run the source by using the following command:
kubectl apply -f kafka-not-secured-source-binding.yaml
Procedure for using the Kamel CLI
Configure and run the source by using the following command:
kamel bind kafka-not-secured-source -p "source.bootstrapServers=The Bootstrap Servers" -p "source.topic=The Topic Names" channel:mychannel
This command creates the KameletBinding in the current namespace on the cluster.
Kafka source
You can use the kafka-not-secured-source
Kamelet as a Kafka source by binding it to a Kafka topic.
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: kafka-not-secured-source-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: kafka-not-secured-source
properties:
bootstrapServers: The Bootstrap Servers
topic: The Topic Names
sink:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
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
-
Save the
kafka-not-secured-source-binding.yaml
file to your local drive, and then edit it as needed for your configuration. -
Run the source by using the following command:
kubectl apply -f kafka-not-secured-source-binding.yaml
Procedure for using the Kamel CLI
Configure and run the source by using the following command:
kamel bind kafka-not-secured-source -p "source.bootstrapServers=The Bootstrap Servers" -p "source.topic=The Topic Names" kafka.strimzi.io/v1beta1:KafkaTopic:my-topic
This command creates the KameletBinding in the current namespace on the cluster.