Schema Registry Cluster

[IgorShcherbakov]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

I couldn't find any more information about connecting the schema registry in the documentation. The basic example connects one node, schemaRegistry: http://schema-registry:8085. While experimenting, I noticed that you can connect two nodes, schemaRegistry: "http://schema-registry-1:8081,http://schema-registry-2:8081." This raises the question: is this a bug or a feature? Was working with the schema registry cluster intended?

Expected behavior

No response

Your installation details

v1.3.0

Steps to reproduce

Screenshots

No response

Logs

No response

Additional context

No response

[github-actions]

Hi IgorShcherbakov! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.