[ https://issues.apache.org/jira/browse/GEODE-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated GEODE-9235: ---------------------------------- Labels: pull-request-available (was: ) > Allow members binding to all addresses > -------------------------------------- > > Key: GEODE-9235 > URL: https://issues.apache.org/jira/browse/GEODE-9235 > Project: Geode > Issue Type: Improvement > Reporter: Alberto Bustamante Reyes > Assignee: Alberto Bustamante Reyes > Priority: Major > Labels: pull-request-available > > *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). -- This message was sent by Atlassian Jira (v8.3.4#803005)