starlingx/docs
Code Issues Proposed changes

Network address range validation is enhanced to configure smaller ranges

Browse Source 
Updated Patchset 1 comments
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: Ib363c0a558480b30b4337949f486168eb903b7b4
This commit is contained in:
Juanita-Balaraj 2021-12-12 22:57:33 -05:00
parent baff361d45
commit 237d9261de
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/planning/kubernetes/network-requirements.rst
View File

@ -13,6 +13,16 @@ Available networks include the optional |PXE| boot network, the internal
management network, the cluster host network, the |OAM| network, and other management network, the cluster host network, the |OAM| network, and other
optional networks for external network connectivity. optional networks for external network connectivity.
.. note::
If you have a small number of nodes, smaller IP subnets / address
ranges should be used to preserve IP addresses that make the network
more manageable. When planning the system architecture an (optional) PXE boot,
management and cluster-host address is required for each node.
PXE Boot network is not "required" in all scenarios; in some scenarios
(e.g. IPv4 and non-vlan-tagged management networks), the management network
can be used for PXE booting.
The internal management network is required by all deployment configurations The internal management network is required by all deployment configurations
for internal communication. for internal communication.