docs/doc/source/planning/kubernetes/shared-vlan-or-multi-netted-ethernet-interfaces.rst

Shared (VLAN or Multi-Netted) Ethernet Interfaces

The management, , cluster host, and other networks for container workload external connectivity, can share Ethernet or aggregated Ethernet interfaces using tagging or IP Multi-Netting.

The internal management cluster host, and other external networks, can use tagging or IP Multi-Netting, allowing them to share an Ethernet or aggregated Ethernet interface with other networks. If the internal management network is implemented as a -tagged network then it must be on the same physical interface used for booting.

The following arrangements are possible:

• One interface for the internal management network and internal cluster host network using multi-netting, and another interface for (on which container workloads are exposed externally). This is the default configuration.
• One interface for the internal management network and another interface for the external and external cluster host (on which container workloads are exposed externally) networks. Both are implemented using tagging.
• One interface for the internal management network, another interface for the external network, and a third for an external cluster host network (on which container workloads are exposed externally).
• One interface for the internal management network and internal cluster host network using multi-netting, another interface for and a third interface for an additional network on which container workloads are exposed externally.

For some typical interface scenarios, see Hardware Requirements <starlingx-hardware-requirements>.

Options to share an interface using tagging or Multi-Netting are presented in the Ansible Bootstrap Playbook. To attach an interface to other networks after configuration, you can edit the interface.