From b3a1627ff968c32004eec5977623341a9a4042bb Mon Sep 17 00:00:00 2001 From: Juanita-Balaraj Date: Sun, 12 Dec 2021 22:57:33 -0500 Subject: [PATCH] Network address range validation is enhanced to configure smaller ranges Updated Patchset 1 comments Signed-off-by: Juanita-Balaraj Change-Id: Ib363c0a558480b30b4337949f486168eb903b7b4 (cherry picked from commit 237d9261de6bef54a9e7f673c06536ae6a676047) --- .../planning/kubernetes/network-requirements.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/source/planning/kubernetes/network-requirements.rst b/doc/source/planning/kubernetes/network-requirements.rst index d7b7b3eca..348ed27dc 100644 --- a/doc/source/planning/kubernetes/network-requirements.rst +++ b/doc/source/planning/kubernetes/network-requirements.rst @@ -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 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 for internal communication.