Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
thecloudgarage opened this issue Jun 5, 2024 · 0 comments
Open

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

thecloudgarage opened this issue Jun 5, 2024 · 0 comments
Labels
external An issue, bug or feature request filed from outside the AWS org

Comments

@thecloudgarage
Copy link

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.
@abhay-krishna abhay-krishna added the external An issue, bug or feature request filed from outside the AWS org label Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
external An issue, bug or feature request filed from outside the AWS org
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@abhay-krishna @thecloudgarage