alb3rtobr opened a new pull request #6435: URL: https://github.com/apache/geode/pull/6435
**AS A** geode contributor **I WANT TO** be able to start members with option `--bind-address=0.0.0.0`, `--bind-address=::` or `--bind-address=*` **SO THAT** all TCP endpoints are bound to all interfaces. It is not currently possible to start cluster members binding to all interfaces. That is using `--bind-address=0.0.0.0` for ipv4 or `--bind-address=::` for ipv6. Geode binds the locator and server traffic port by default to `0.0.0.0`, but the membership ports are bound by default to the local address. Changing the default membership binding is not the best option, as it could cause problems in existing Geode deployments. But using `--bind-address=0.0.0.0`, `--bind-address=::` or `--bind-address=*` should be accepted. There is a use case that needs this binding, that is using Istio with Geode. One of the requirements set by Istio towards applications trying to integrate with it is that the application listening ports need to be bound to 0.0.0.0 address (which listens on all interfaces). It is currently not possible to start a cluster using wildcard address due to if `--bind-address` is specified, its value will be used for all tcp endpoints and the udp membership endpoint created by JGroups. And as JGroups does not accept binding to all addresses, and exception is thrown. This behavior can be verified with `WildcardAddressBindingDUnitTest.java` tests. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
