Kafka Connect

This reference introduces the Kafka Connect component, how it differs from the Axual Connect component it replaces, and the pages that cover its concepts, deployment, chart values and diagnosis.

Type

Reference

Goal

Find the Kafka Connect page that covers the concept, procedure or value you need.

Audience

Platform Operators and Tenant Admins who deploy or register Kafka Connect clusters.

When to use

Use this guide as the entry point to the Kafka Connect documentation.

Contents

The sections below cover each area of the component:

What Kafka Connect gives each tenant

Kafka Connect gives every tenant its own Apache Kafka Connect cluster, deployed and managed by the Strimzi operator and driven from Axual Self-Service. Each cluster runs its own worker pods, its own internal topics and its own connector credentials, so the connectors of one tenant cannot affect the throughput or stability of another.

It replaces Axual Connect, which gives all tenants on an instance a single shared cluster. Axual Connect is deprecated (see Why Kafka Connect replaces Axual Connect for the timeline), so new installations use Kafka Connect. To move an existing installation across, follow Migrating from Axual Connect to Kafka Connect.

Where to go next

The pages below cover the component from concepts through to deployment, diagnosis and removal: