Docs Self-Managed Manage Redpanda Console Configuration Kafka Connect Connect Redpanda Console to Kafka Connect Clusters 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. Prerequisites You must deploy a Kafka Connect cluster separately before configuring Redpanda Console to connect to it. 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 Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution Deserialization Topic Documentation