Fix incorrect information about swarm port assignment

This commit is contained in:
Misty Stanley-Jones 2016-10-10 10:02:15 -07:00
parent 4a833da9f3
commit 220bbed0e4
1 changed files with 3 additions and 1 deletions

View File

@ -74,7 +74,9 @@ run on the assigned node or fail.
The swarm manager uses **ingress load balancing** to expose the services you The swarm manager uses **ingress load balancing** to expose the services you
want to make available externally to the swarm. The swarm manager can want to make available externally to the swarm. The swarm manager can
automatically assign the service a **PublishedPort** or you can configure a automatically assign the service a **PublishedPort** or you can configure a
PublishedPort for the service in the 30000-32767 range. PublishedPort for the service. You can specify any unused port. If you do not
specify a port, the swarm manager assigns the service a port in the 30000-32767
range.
External components, such as cloud load balancers, can access the service on the External components, such as cloud load balancers, can access the service on the
PublishedPort of any node in the cluster whether or not the node is currently PublishedPort of any node in the cluster whether or not the node is currently