-
Notifications
You must be signed in to change notification settings - Fork 912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow the ability to specify UDP or TCP for service discovery metadata #244
Comments
I'm having same issue with Elastic search and port 9300 being open for both TCP and UDP when I use ephemeral ports: This propogates into regstrator as: So what is in consul doesn't tell me which one is TCP and UDP. I think the fault is more of docker assigning different port to port 9300, but trying to dynamically query what port 9300/tcp is impossible. I'm probably doing to just pick some hard coded ports and move on, but I seem to keep running to reasons why container instances need to be pinned to a docker host or a specific port (I'm trying to run this container in a swarm cluster, and getting the IP address to advertise is a pain that I though I could solve by querying consul). |
@brendangibat I'm having a similar issue where I want to be able to specify |
@brendangibat I just needed to do the same thing and was surprised to find this feature missing, so I've gone ahead and implemented this (please refer to PR #668). As this is almost 4 years later, I suspect you may not need the feature anymore, however.. |
Also forgot to mention, I've also uploaded a new docker image with this PR included already, which you can pull from adaptant/registrator should this be useful for anyone needing this functionality now. |
I'm exposing ports 9200 / TCP and UDP for an ElasticSearch container, specifying the service name for the port doubles the consul entries for DNS resolution. I would like the ability to do something such as SERVICE_9200_UDP_IGNORE / SERVICE_9200_TCP_IGNORE or SERVICE_9200_UDP_NAME = "udp-service".
The text was updated successfully, but these errors were encountered: