opened 09:05PM - 27 Aug 15 UTC
closed 10:58PM - 02 May 17 UTC
type/enhancement
Just a question about best practices here..
We have internal services which exp… ose multiple ports (similar to, say, Zookeeper or Consul itself) but the service definition within Consul only allows for a single port per service.
It is possible to configure multiple services, each with their own id, which seems to be the default for registrator, though that adds complications in things like health checks, maintenance mode, etc.
Another option would be to have a unique service id and then just store the ports somewhere in the consul KV store, keyed by the service id, though that would be a bunch of extra calls and it would be nice to have it all encapsulated in the service definition.
We are running in to this problem because on one host we have 1 consul container and various other containers, two of which may contain the same service, in which case they would need to use different ports, and we would need that to be easily discoverable.
Any thoughts?
Thanks!
The above question was asked back in 2016 so i wanted to know if same holds true in 2022 as well that to reach a service like this http://my-service.service.consul i still need to a proxy or there is some other way where i can do this without proxy in consul?
Thanks