
Fixed typo in LetsEncrypt example Removed duplicate Datanet entry from main index.rst Reworked Use Kubernetes CPU Manager Static Policy prerequisite block. Restored fault/index version of FM toctree in top-level index. Added merged doc entries to top level index.rst. Incorporated review comments. Also some generic formatting clean-up such as converting abbreviations to rST-style :abbr: markup. Moved url with embedded substitution out of code-block. Addressed patch 2 review comments. Some addtional rST tidying. See comment replies for open questions/issues. This patch fixes an issue with 'stx' in filenames that may differ downstream using-an-image-from-the-local-docker-registry-in-a-container-spec new substitution and changing code-blocks to parsed-literals as required. Initial submission for review. Note that a couple of references to WR persist in examples. These will be marked up with comments in the review. Signed-off-by: Stone <ronald.stone@windriver.com> Change-Id: I1efef569842caff5def9dc00395b594d91d7a5d0 Signed-off-by: Stone <ronald.stone@windriver.com>
23 lines
659 B
ReStructuredText
23 lines
659 B
ReStructuredText
|
|
.. viy1592399797304
|
|
.. _nodeport-usage-restrictions:
|
|
|
|
===========================
|
|
NodePort Usage Restrictions
|
|
===========================
|
|
|
|
This sections lists the usage restrictions of NodePorts for your |prod-long| product.
|
|
|
|
The following usage restrictions apply when using NodePorts:
|
|
|
|
.. _nodeport-usage-restrictions-ul-erg-sgz-1mb:
|
|
|
|
- Ports in the NodePort range 31,500 to 32,767 are reserved for applications
|
|
that use Kubernetes NodePort service to expose the application externally.
|
|
|
|
- Ports in the NodePort range 30,000 to 31,499 are reserved for |prod-long|.
|
|
|
|
.. only:: partner
|
|
|
|
.. include:: ../_includes/nodeport-usage-restrictions.rest
|