starlingx/docs
Code Issues Proposed changes

Describe K8S NodePorts restrictions

Browse Source 
Closes-Bug: 1874823

Change-Id: Ia45aab96bc7aa512c941d555d052edde9a925417
Signed-off-by: MCamp859 <maryx.camp@intel.com>
This commit is contained in:
MCamp859 2020-07-07 16:28:13 -04:00
parent 579746ed4b
commit 0c793580c3
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/operations/index.rst
View File

@ -31,6 +31,7 @@ Kubernetes Operation
k8s_cluster k8s_cluster
k8s_docker_reg_management k8s_docker_reg_management
k8s_nodeport_usage
k8s_persistent_vol_claims k8s_persistent_vol_claims
k8s_sriov_config k8s_sriov_config
k8s_qat_device_plugin k8s_qat_device_plugin

12
doc/source/operations/k8s_nodeport_usage.rst Normal file
View File

@ -0,0 +1,12 @@
=========================
Kubernetes NodePort Usage
=========================
The following usage restrictions apply when using NodePorts:
* NodePorts 30,000 to 31,499 are **reserved** for the StarlingX
Platform and additional StarlingX applications that are supported on top of
the StarlingX Platform (for example, StarlingX OpenStack).
* NodePorts 31,500 to 32,767 are available for applications that use the
Kubernetes NodePort service to expose the application externally.