You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Kafka Inlets are returning to the client the bind address when specifying how to connect to a broker. This prevents from using any bind address which is not an accessible address (127.0.0.1 or 192.168.0.1 are ok, but any mask like 0.0.0.0 is not).
Kafka server solves the issue by using the concept of "advertised address", which is independent from the bind address and it's just returned to the client as-is. We should implement it.
The text was updated successfully, but these errors were encountered:
Currently, Kafka Inlets are returning to the client the bind address when specifying how to connect to a broker. This prevents from using any bind address which is not an accessible address (
127.0.0.1
or192.168.0.1
are ok, but any mask like0.0.0.0
is not).Kafka server solves the issue by using the concept of "advertised address", which is independent from the bind address and it's just returned to the client as-is. We should implement it.
The text was updated successfully, but these errors were encountered: