From 784fc22c7e09b2e2443a61bed2a2701eb151dbae Mon Sep 17 00:00:00 2001 From: Peter Novotnak Date: Thu, 11 Jun 2015 18:08:21 -0700 Subject: [PATCH] Added default allowable port range for NodePort to the docs. --- docs/services.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/services.md b/docs/services.md index 2c155e17855..c905f139a1a 100644 --- a/docs/services.md +++ b/docs/services.md @@ -315,10 +315,11 @@ as of Kubernetes 1.0. ### Type = NodePort If you set the `type` field to `"NodePort"`, the Kubernetes master will -allocate you a port (from a flag-configured range) on each node for each port -exposed by your `Service`. That port will be reported in your `Service`'s -`spec.ports[*].nodePort` field. If you specify a value in that field, the -system will allocate you that port or else will fail the API transaction. +allocate you a port (from a flag-configured range, default: 30,000 - 32,767) +on each node for each port exposed by your `Service`. That port will be +reported in your `Service`'s `spec.ports[*].nodePort` field. If you specify +a value in that field, the system will allocate you that port or else will +fail the API transaction. This gives developers the freedom to set up their own load balancers, to configure cloud environments that are not fully supported by Kubernetes, or