You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case where a Nomad host will have containers binding to multiple interfaces (one physical, multiple VLAN interfaces). A single gocast instance will see all containers/advertised ports on a single Consul node "equally". The connection to the TOR will go over the default route / single connection.
Would it be possible to make enable_gocast tag configurable to allow for multiple gocast instances running to each find separate groups of Consul services to advertise? The matchTag looks in a good spot to pull from the agent config with other Consul config values.
The text was updated successfully, but these errors were encountered:
@philipcristiano Yes, I have this staged in a branch as part of enabling ipv6 support. It still needs to be tested and will be a few weeks, but I can put this in a PR and if you would be able to test this for your use case, that would be great !
I have a use case where a Nomad host will have containers binding to multiple interfaces (one physical, multiple VLAN interfaces). A single gocast instance will see all containers/advertised ports on a single Consul node "equally". The connection to the TOR will go over the default route / single connection.
Would it be possible to make
enable_gocast
tag configurable to allow for multiple gocast instances running to each find separate groups of Consul services to advertise? ThematchTag
looks in a good spot to pull from the agent config with other Consul config values.The text was updated successfully, but these errors were encountered: