You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: