Event Target for Confluent
This event Target receives CloudEvents and forwards the event to a Confluent Kafka cluster.
- Access to a Kafka cluster with appropriate configuration details
If a password is required, consult the Secrets guide for additional information on how to add the password as a secret.
Kafka Cluster Details
Depending on the cluster and user permissions, the Kafka topic must
exist prior to setting up the target. Otherwise, the Target will attempt to create
the topic which will require setting the
Topic replication and
Deploying an Instance of the Target
Open the Bridge creation screen and add a Target of type
In the Target creation form, provide a name for the event Target and add the following information:
- Password Secret: Reference to a TriggerMesh secret containing the password associated with the user accessing the Kafka cluster as discussed in the prerequisites.
- Bootstrap Servers: Confluent bootstrap servers to connect to. Use the
ADD MOREbutton to add additional bootstrap servers if needed.
- Topic: Confluent topic to publish events to.
- Topic Replication: Number of copies of the topic that should exist in the cluster.
- Topic Partitions: Number of partitions for the topic to allow for concurrency.
- SASL Mechanism: Denote how to authenticate against Kafka. Value can be either
- Security Protocol: Denote whether to encrypt the password using SSL/TLS.
- Username: The username to connect to the Kafka cluster as. This field must have a value even if the cluster allows unauthenticated access.
There is an optional toggle flag indicating if the full CloudEvent should be sent to Confluent. By default, this is disabled which means only the event payload will be sent.
After clicking the
Save button, the console will self-navigate to the Bridge editor. Proceed by adding the remaining components to the Bridge.
After submitting the Bridge, and allowing for some configuration time, a green check mark on the main Bridges page indicates that the Bridge with a Confluent event Target was successfully created.
For more information on how to configure Confluent, refer to the Confluent documentation.
The Confluent event Target leaves the CloudEvent type definition to the discretion of the implementer. In addition, no events are produced as a response.