starlingx/docs
Code Issues Proposed changes
docs/doc/source/planning/kubernetes/internal-management-network-planning.rst
Ron Stone 2b62f49a9d Fix symlinks 
Changed paths to avoid '..', which breaks symlinks in newer versions of sphinx.
Consolidated installation include files under /_includes. Prefixed r5 versions with 'r5_'
Moved files that are used up/down, but at different paths under /shared/_includes
and /shared/figures
Move two include files to /_includes
Moved addtional images to /shared/figures/... Required for DS platform builds.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ia38f4205c5803b3d1fc043e6c59617c34a4e5cbd
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
2021-09-02 13:31:45 +00:00

2.6 KiB
Executable File
Raw Blame History

Kubernetes Internal Management Network Planning

The internal management network is a private network, visible only to the hosts in the cluster.

Note

This network is not used with Simplex systems.

You must consider the following guidelines:

  • The internal management network is used for booting of new hosts, and must be untagged. It is limited to IPv4, because the installer does not support IPv6 booting. For example, if the internal management network needs to be on a -tagged network for deployment reasons, or if it must support IPv6, you can configure the optional untagged boot network for booting of new hosts using IPv4.

  • You can use any 1 GB or 10 GB interface on the hosts to connect to this network, provided that the interface supports network booting and can be configured from the BIOS as the primary boot device.

  • If static IP address assignment is used, you must use the system host-add command to add new hosts, and to assign IP addresses manually. In this mode, new hosts are not automatically added to the inventory when they are powered on, and they display the following message on the host console:

    This system has been configured with static management
and infrastructure IP address allocation. This requires
that the node be manually provisioned in System
Inventory using the 'system host-add' CLI, GUI, or
stx API equivalent.

  • For the IPv4 address plan, use a private IPv4 subnet as specified in RFC

    1. This helps prevent unwanted cross-network traffic on this network.

    It is suggested that you use the default subnet and addresses provided by the controller configuration script.

  • You can assign a range of addresses on the management subnet for use by the . If you do not assign a range, takes ownership of all available addresses.

  • On systems with two controllers, they use IP multicast messaging on the internal management network. To prevent loss of controller synchronization, ensure that the switches and other devices on these networks are configured with appropriate settings.

partner