github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #9697 from CyrusBiotechnology/cyrus/feature/nodeport-documentation 

Added what seems to be the default allowable port range for NodePort to the docs
pull/6/head
Fabio Yeon 2015-06-15 19:32:35 -07:00
parent 9b3e9a509d 784fc22c7e
commit 6ab2aee677
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/services.md
View File

@ -315,10 +315,11 @@ as of Kubernetes 1.0.
### Type = NodePort ### Type = NodePort
If you set the `type` field to `"NodePort"`, the Kubernetes master will 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 allocate you a port (from a flag-configured range, default: 30,000 - 32,767)
exposed by your `Service`. That port will be reported in your `Service`'s on each node for each port exposed by your `Service`. That port will be
`spec.ports[*].nodePort` field. If you specify a value in that field, the reported in your `Service`'s `spec.ports[*].nodePort` field. If you specify
system will allocate you that port or else will fail the API transaction. 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 This gives developers the freedom to set up their own load balancers, to
configure cloud environments that are not fully supported by Kubernetes, or configure cloud environments that are not fully supported by Kubernetes, or