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

How do we handle processes that don't care what port they bind to? #6

Open
alexras opened this issue Dec 2, 2022 · 0 comments
Open

Comments

@alexras
Copy link
Collaborator

alexras commented Dec 2, 2022

Some processes will want to bind to some random high-numbered port, as long as it knows there are no collisions with that port on its parent host. In EKS, this is trivial - NodePort services take care of the port assignment, and individual processes can just advertise a fixed, lower-numbered port. In Docker and other less batteries-included runtimes, this gets a little trickier, since we'd have to make sure we're not colliding ports at process-start-time.

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

1 participant