-
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
Port selection for Connect envoy when network.port.to is used #9824
Comments
So we do what you're looking for in the following manner (essentially) We make sure the port we want to receive inbound traffic on is registered with the service (9090 in this case). Then we listen for it on 0.0.0.0:9090
and
I'm not sure what the "right" way of doing it is, but this might get you rolling :) |
I do want to use named ports, though. At the very least, it seems silly to have named ports and then not being able to use them for anything useful. But fundamentally, it doesn't matter what I'm trying to do. A definition that looks like my OP produces a proxy setup that is critically misconfigured and surely that's a bug. |
I should add, I've already got my setup working. Not the issue. |
Nomad version
Nomad v1.0.2 (4c1d4fc)
Operating system and Environment details
Issue
Given a job that looks like this:
The envoy sidecar will get configured to connect to
127.0.0.1:12345
where 12345 is the dynamic port allocated forhttp
. That may not connect! (In my setup that port is on the host's interface instead.) It should be theto
port.Current workaround is to specify:
This may possibly be related to #9730?
The text was updated successfully, but these errors were encountered: