CLI for connectors, self-service Connect, and Console HA

Manage connectors via CLI

Deploy and manage Kafka Connect resources using infrastructure as code.

---
apiVersion: kafka/v2
kind: Connector
metadata:
  connectCluster: kafka-connect
  name: click.my-connector
  labels:
    conduktor.io/auto-restart-enabled: true
    conduktor.io/auto-restart-frequency: 600
spec:
  config:
    connector.class: 'org.apache.kafka.connect.tools.MockSourceConnector'
    tasks.max: '1'
    topic: click.pageviews

Grant connector ownership to application teams

Application teams can manage their connectors through self-service by adding connector ownership to application instances.

---
apiVersion: self-service/v1
kind: ApplicationInstance
metadata:
  application: "clickstream-app"
  name: "clickstream-dev"
spec:
  cluster: "shadow-it"
  serviceAccount: "sa-clicko"
  resources:
    - type: CONNECTOR
      connectCluster: shadow-connect
      patternType: PREFIXED
      name: "click."

View connector status over time

The Kafka Connect UI now shows connector status graphs over time and connector previews on the cluster selection screen.

Deploy multiple Console instances for HA

Multiple Console instances can run in parallel. Only one instance handles Kafka data indexing, so cluster impact stays minimal.

---

For a full list of changes, read the complete release notes.