Streaming
Streaming releases
Beta
0
Supported
0
End of life
0
v25.2
Released
Jul 2025
Ended
Jul 2026
End of life
v25.1
Released
Apr 2025
Ended
Apr 2026
End of life
v24.3
Released
Dec 2024
Ended
Dec 2025
End of life
v24.2
Released
Jul 2024
Ended
Jul 2025
End of life
v24.1
Released
Apr 2024
Ended
Apr 2025
End of life
v23.3
Released
Dec 2023
Ended
Dec 2024
End of life
Kafka Connect
Redpanda Console provides a user interface that lets you manage multiple Kafka Connect clusters. You can inspect or patch connectors; restart, pause, and resume connector tasks; and delete connectors. Redpanda Console queries all configured Kafka Connect clusters for their status, so you have an overview of all your Kafka Connect clusters.
| Redpanda Streaming deployments do not include a Kafka Connect cluster. |
Configuration
For each cluster, provide a unique name, the HTTP address of the cluster, and the authentication settings, if required. The name can be any unique string that helps you to identify the Kafka Connect cluster. See all available configuration options in the Redpanda Console Configuration.
The following sample configuration goes in the configuration file’s root level.
connect:
enabled: true
clusters:
- name: datawarehouse # Required field, will be used as identifier in the frontend
url: http://dwh-connect.mycompany.com:8083
tls:
enabled: false # Trusted certs are still allowed by default
username: admin
# password: # Set using flag --connect.clusters.0.password=secret
- name: analytics # Required field, will be used as identifier in the frontend
url: http://analytics.mycompany.com:8083
# No auth configured on that cluster, hence no username/password set
Was this helpful?