[
https://issues.apache.org/jira/browse/GEODE-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-8877.
---------------------------------------------
Resolution: Won't Fix
> Configurable membership bind address
> ------------------------------------
>
> Key: GEODE-8877
> URL: https://issues.apache.org/jira/browse/GEODE-8877
> Project: Geode
> Issue Type: Improvement
> Reporter: Alberto Bustamante Reyes
> Assignee: Alberto Bustamante Reyes
> Priority: Major
> Labels: pull-request-available
>
> Geode binds the locator and server traffic port by default to 0.0.0.0, but
> the membership ports are bound to the local address.
> There is a use case that needs this binding to be configurable ([link to the
> conversation in the dev list|http://markmail.org/thread/7dwtygtgfcitboy3]):
> We would like to use Istio with Geode. For that, a sidecar container (Envoy)
> has to be added in each Geode pod. That sidecar container intercepts and
> handles all incoming and outgoing traffic for that pod. 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 either localhost or
> 0.0.0.0 address (which listens on all interfaces).
>
> Geode binds the locator and server traffic port by default to 0.0.0.0, but
> the membership ports are bound to the pod IP.
> And with Envoy listening on the pod IP for incoming traffic and proxying
> everything towards localhost, applications binding to pod IPs won't receive
> any traffic.
> We have tried using the "bind-address" parameter, but that doesn't work for
> our case. Geode binds the listening ports to the configured address, but it
> also shares that same address to other members in the system as the address
> to be used to reach it. If we configure that address to localhost, it just
> won't work.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
