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
In some cases, it might be useful for development perspective to have a load balancer listen on one port and sent traffic to the microservice on a different one.
In the local environment, people for ports would because of ports opening do
that way both service A and B are exposed to the user and do not have overlapping ports.
Similarly, if a micro-service has a port defined with <port>:<port>and uses a load-balancer then the load-balancer should have a listener using the first port to target the microservice, and the second port used as the exposed port of the microservice.
The text was updated successfully, but these errors were encountered:
In some cases, it might be useful for development perspective to have a load balancer listen on one port and sent traffic to the microservice on a different one.
In the local environment, people for ports would because of ports opening do
that way both service A and B are exposed to the user and do not have overlapping ports.
Similarly, if a micro-service has a port defined with
<port>:<port>
and uses a load-balancer then the load-balancer should have a listener using the first port to target the microservice, and the second port used as the exposed port of the microservice.The text was updated successfully, but these errors were encountered: