Skip to content
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

Bind to IP #2120

Closed
galileo-pkm opened this issue Mar 10, 2020 · 3 comments
Closed

Bind to IP #2120

galileo-pkm opened this issue Mar 10, 2020 · 3 comments

Comments

@galileo-pkm
Copy link

Requirement - what kind of business use case are you trying to solve?

Good security practice

Problem - what in Jaeger blocks you from solving the requirement?

Feature not available

AFAIK there is no way to bind various jaeger services to a single address.
There are command line switches that bind certain services to host:port combination but not available for all (UI, collector ...)

Proposal - what do you suggest to solve the problem or improve the existing situation?

--bind-to-ip [coma list of IP addresses ] would be useful, especially for jaeger-all-in-one.

@ghost ghost added the needs-triage label Mar 10, 2020
@yurishkuro
Copy link
Member

We have an open ticket #1447 to support host:port CLI flags instead of just ports. What would --bind-to-ip provide in addition to that ticket?

@galileo-pkm
Copy link
Author

I failed to find that issue, I should have posted this as a comment on that one.
--bind-to-ip would set the listening address for all services without specifying the port (keep the default).

@yurishkuro
Copy link
Member

But I think individual host-port flags are more flexible, e.g. you can set collector's inbound port on a public IP, while its admin port on internal IP only.

Feel free to comment on #1447.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants