Support configuring Kafka bootstrap servers both from a single server or multiple servers

[smoya]

Current configuration is limited to just one server, which is used as Kafka bootstrap server. For example:

servers:
    asyncapi-kafka-test:
        url: 'asyncapi-kafka-test-asyncapi-8f90.aivencloud.com:20472'
        protocol: kafka-secure

The event-gateway gets the value of url field and uses it as the only Kafka bootstrap server, mapping it to the same port but locally, meaning :20472 (can be changed through extension). Then it opens a new local port dynamically for each discovered broker (if there are).

However, users might want to configure several Kafka bootstrap servers (actually recommended).

There are several possibilities:

1. To group servers of the same cluster

There is a RFC0 implementation for this: asyncapi/spec#465.

We could support it from day one via extensions: x-cluster field or similar. Or rather add it as official change in the Kafka binding.

2. To add a new extension to the existing server

Support only one server, and add the rest of bootstrap servers in a new extension like x-extra-bootstrap-servers.

I'm completely leaning towards the first. But open to suggestions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️