aws / aws/eks-anywhere

Bare Metal- Segregate control plane and data plane traffic on seperate NIC/VLANs

Open
#8,250 0 comments 2 reactions 0 assignees View on GitHub
area/providers external
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

Hi,

My worker nodes are configured with 2x100Gig and 2x25Gig network interface cards. My control plane node is configured with 2x25Gig network interface card. Is there a possibility or is it a valid configuration to separate the control plane traffic to go over the 2x25Gig leaving 100Gig interfaces for data plane. Obviously, the consideration would be to place 2x100Gig and 2x25Gig on worker nodes in separate vlans. Is this is a valid configuration. Will Tinkerbell support it in hardware.csv to configure multiple interfaces with different subnets.

Contributor guide

Open the contributing guide

Research direction

Start with the Tinkerbell hardware.csv configuration mentioned in the issue and determine whether it can represent multiple NICs with separate subnets or VLANs. Done means the validity of segregating control-plane and data-plane traffic is established, along with the supported hardware.csv representation or a clearly identified limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
infrastructure, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.