From 220bbed0e4888c77ae343ad1f4aae12b0610cffb Mon Sep 17 00:00:00 2001 From: Misty Stanley-Jones Date: Mon, 10 Oct 2016 10:02:15 -0700 Subject: [PATCH] Fix incorrect information about swarm port assignment --- engine/swarm/key-concepts.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/engine/swarm/key-concepts.md b/engine/swarm/key-concepts.md index 302e452775..94b74dae86 100644 --- a/engine/swarm/key-concepts.md +++ b/engine/swarm/key-concepts.md @@ -74,7 +74,9 @@ run on the assigned node or fail. The swarm manager uses **ingress load balancing** to expose the services you want to make available externally to the swarm. The swarm manager can 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 PublishedPort of any node in the cluster whether or not the node is currently