starlingx/docs
Code Issues Proposed changes

update pxeboot network requirements (dsr10)

Browse Source 
Change-Id: I467db82e3faedfdcf3b4314cddbbc7c099b2030f
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili 2025-01-15 19:14:40 +00:00
parent cb79fdf98f
commit ead65eebe4
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/source/deploy/kubernetes/common-components.rst
View File

@ -146,16 +146,21 @@ A number of components are common to most |prod| deployment configurations.
An *optional* network over which nodes net boot from controllers.
By default, controllers network boot other nodes over the management
network. This network is required for a variety of special case situations
network. The PxeBoot network is required for a variety of special case situations
where the management network cannot be used to boot the other nodes:
- The management network must be IPv6. IPv4 pxeboot network must be
configured since IPv6 does not support pxeboot.
- When the management network must be IPv6, an IPv4 PxeBoot network must be
configured since IPv6 does not support PxeBoot. In this case, the
management network also needs to be vlan tagged.
- The management network must be vlan tagged. Most servers' BIOS do not
support pxebooting over a tagged network, so an untagged pxeboot
- When the management network must be vlan tagged, most servers' BIOS do not
support pxebooting over a tagged network, so an untagged PxeBoot
network must be configured.
- If the system is dual-stack (IPv4 and IPv6) and IPv6 is chosen as the
primary address pool family. To identify the primary pool, see
:ref:`dual-stack-support-318550fd91b5`.
**Node Interfaces**
In general, node network interfaces can optionally be: