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

Allow Configuration of Bind Address of Envoy and Diagd Processes #2293

Closed
josuesdiaz opened this issue Feb 10, 2020 · 2 comments
Closed

Allow Configuration of Bind Address of Envoy and Diagd Processes #2293

josuesdiaz opened this issue Feb 10, 2020 · 2 comments
Labels
t:feature New feature or enhancement request
Milestone

Comments

@josuesdiaz
Copy link
Contributor

Currently, Envoy and Diagd processes are always listening on 0.0.0.0, which is all IPv4 addresses.

To assist in creating a workaround for those who want to bind to IPv6 (namely "::"), this change would allow the usage of environment variables AMBASSADOR_DIAGD_BIND_ADDRESS and AMBASSADOR_ENVOY_BIND_ADDRESS to configure how the services are listening.

As well, this change would allow those who want to limit the processes to a specific IP address, rather than all-IPv4 or all-IPv6.

@josuesdiaz
Copy link
Contributor Author

@josuesdiaz
Copy link
Contributor Author

Think we should be all set with this Issue now. Env vars for chaging bind address of processes are:
AMBASSADOR_ENVOY_BIND_ADDRESS
AMBASSADOR_DIAGD_BIND_ADDRESS

For those interested in binding these to all IPv6 addresses, the following values should work
AMBASSADOR_ENVOY_BIND_ADDRESS: "::"
AMBASSADOR_DIAGD_BIND_ADDRESS: "[::]"

@khussey khussey added the t:feature New feature or enhancement request label Feb 19, 2020
@khussey khussey added this to the 1.y Cycle 1 milestone Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:feature New feature or enhancement request
Projects
None yet
Development

No branches or pull requests

2 participants