-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Impossible to use consul connect with the deprecated port_map syntax #9200
Comments
Apologies for the brevity but I'm on my phone 😀 The service stanza, even for the HC, needs to be at the group level. Here's a snippet from one of our job files
Note that the network section of your task will need to be removed too It's also possible to use the expose tag (which I can provide an example of too) if all you're trying to do is keep the health check. Just depends on your use case Hopefully this gets your started but if not I can give you a more flushed out sample in the morning |
Hi @idrennanvmware ! Thank you for the example, it works perfectly fine for our needs :) Thank you for your help :) |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Hi there !
Nomad version
Nomad v0.12.7
Operating system and Environment details
Debian Buster
Issue
I'm trying to get Consul Connect working to allow my backend to reach my redis server.
I'm using the deprecated port_map syntax as adviced in the issue #8780 as I need healthchecks and service tags, but as soon as I add the network stanza in bridge mode, I'm getting the following error when deploying:
If I delete my task-service stanza, and use the new syntax, everything runs fine, but I actually need my healthchecks and tags.
Is there anything I'm missing ? Is there a workaround to get it work ?
Job file
Here is a snippet of my job file, especially the task group in error
Thank you for your help :)
The text was updated successfully, but these errors were encountered: