redpanda: Support multiple listeners

[BenPope]

See: https://cwiki.apache.org/confluence/display/KAFKA/KIP-103%3A+Separation+of+Internal+and+External+traffic

#98 highlights the problem; there are multiple networks - the docker network for the composed containers, as well as host. The advertised addresses need to be different, depending on which network the connection comes from.

[rkruze]

Another user ran into this issue on the community slack channel. https://vectorizedcommunity.slack.com/archives/C01B3QBLUTT/p1610603088004800

[dotnwat]

@rkruze should be in next week!

[raphaelauv]

@dotnwat do you have some news about this ? Thank you :)

[dotnwat]

hi @raphaelauv yes support for multiple listeners has merged (since v21.1.2), and yesterday some of the tool support to interact with the new configuration settings merged. we've tested docker compose and k8s with multiple network setups and it seems to be working ok.

until a release with the tooling update is cut, the configuration file can be changed manually:

  # Multiple listeners are also supported as per KIP-103.
  # The names must match those in kafka_api
  advertised_kafka_api:
  - address: 0.0.0.0
    name: internal
    port: 9092
  - address: redpanda-0.my.domain.com.
    name: external
    port: 9093

kafka_api:
  - <similar>

I'm pretty sure I update some ticket when those changes landed, but I definitely missed this one. Sorry about that. Let us know if you run into any issues getting it working.

[emaxerrno]

@raphaelauv we aim to have this release next week. AFAIK it's supported through and through on every level now. We just need to cut the release.

[BenPope]

This is fixed.

[dotnwat]

This is fixed.

thank you!