3143d86b69
Updates for patchset 2 review comments Changed link depth of main Planning index and added some narrative guidance Added planning/openstack as sibling of planning/kubernetes Related additions to abbrevs.txt Added max-workers substitution to accomodate StarlingX/vendor variants Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ibff9af74ab3f2c00958eff0e33c91465f1dab6b4 Signed-off-by: Stone <ronald.stone@windriver.com>
2.5 KiB
Executable File
Kubernetes L2 Access Switches
L2 access switches connect the hosts to the different networks. Proper configuration of the access ports is necessary to ensure proper traffic flow.
One or more L2 switches can be used to connect the hosts to the different networks. When sharing a single L2 switch you must ensure proper isolation of network traffic. A sample configuration for a shared L2 switch could include:
- one port-based for the internal management network with internal cluster host network sharing this same L2 network (default configuration)
- one port-based for the network
- one or more sets of for additional networks for external network connectivity
When using multiple L2 switches, there are several deployment possibilities:
- A single L2 switch for the internal management cluster host and networks. Port or -based network isolation is mandatory.
- An additional L2 switch for the one or more additional networks for external network connectivity.
- Redundant L2 switches to support link aggregation, using either a
failover model, or for more robust redundancy. For more information, see
Redundant Top-of-Rack Switch Deployment Considerations <redundant-top-of-rack-switch-deployment-considerations>.
Switch ports that send tagged traffic are referred to as trunk ports. They participate in from the moment the link goes up, which results in a several second delay before the trunk port moves to the forwarding state. This delay will impact services such as and that are used during regular operations of .
You must consider configuring the switch ports, to which the management interfaces are attached, to transition to the forwarding state immediately after the link goes up. This option is referred to as a PortFast.
You should consider configuring these ports to prevent them from participating on any exchanges. This is done by configuring them to avoid processing inbound and outbound packets completely. Consult your switch's manual for details.
Redundant Top-of-Rack Switch Deployment Considerations <redundant-top-of-rack-switch-deployment-considerations>