Skip to main content
The Kafka Target Connector defines the Apache Kafka cluster where your pipelines write output events, enabling Kafka-to-Kafka replication through Popsink. Use it to relay, fan out, or bridge event streams between clusters — for example from an on-premises cluster to a cloud-managed one — while applying Popsink transformations in between. This target only stores the broker connection and authentication for the sink cluster: source topics and consumer groups are configured on the Kafka source connector and on your subscriptions.

​
Table of Contents

  1. Compatible versions
  2. Key Features
  3. Prerequisites
  4. Configuration
  5. Security Protocols

​
Compatible versions

Brokers older than 2.1 are not supported — the client negotiates API versions with the cluster and no longer implements the pre-2.1 protocol.

​
Key Features

  • Kafka-to-Kafka pipelines: bridge event streams between clusters with Popsink transformations applied in flight.
  • Broad authentication support: PLAINTEXT, SSL, and SASL (PLAIN, SCRAM-SHA-256, SCRAM-SHA-512, OAUTHBEARER, GSSAPI).
  • Topic passthrough: output topic names follow your subscription configuration — no renaming is imposed by the target.

​
Prerequisites

  • A reachable Kafka cluster to use as the sink.
  • Credentials with permission to produce to the target topics (and to create them, if they don’t pre-exist and auto-creation is disabled on the cluster).

​
Configuration

​
Security Protocols