> Is there any way to configure a bind address to be used only for membership?
To your first question, I asked around but I’m not aware of anything like what you are looking for. What you are describing does seem like it could become a common setup on Kubernetes, but I personally haven’t tried using Geode with Istio and Envoy. Please share what you learn! > I thought that it will be interesting to take a look at how the membership > works (how the distributed system is created), to check if at some point I > could decouple how the value of "bind-address" parameter is used to configure > binding and to indicate other members that they can reach the new member at > that hostname. Any comment about what I should check first is welcome. Maybe someone with more experience in the membership code could comment on this? Aaron > On Jan 20, 2021, at 9:07 AM, Alberto Bustamante Reyes > <alberto.bustamante.re...@est.tech> wrote: > > It seems this is not a trendic topic... 🙂 Let me share my approach by the > moment, maybe this will receive more comments: > > I thought that it will be interesting to take a look at how the membership > works (how the distributed system is created), to check if at some point I > could decouple how the value of "bind-address" parameter is used to configure > binding and to indicate other members that they can reach the new member at > that hostname. Any comment about what I should check first is welcome. > > Thanks! > > BR/ > > Alberto Bustamante > > > > > > ________________________________ > De: Alberto Bustamante Reyes <alberto.bustamante.re...@est.tech> > Enviado: martes, 19 de enero de 2021 1:45 > Para: dev@geode.apache.org <dev@geode.apache.org> > Asunto: Different binding addresses for traffic & membership > > Hi geode-devs, > > I have a question related with Geode & Kubernetes: > 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. > > Is there any way to configure a bind address to be used only for membership? > I have not seen any configuration parameter or property that could be useful > to solve this problem, maybe I missed it. > > Thanks in advance, > > BR/ > > Alberto Bustamante
