HCI Network Interfaces for management and Edge network when creating HCI Cluster

Should I first create a subinterfaces and then use subinterface eg.
subinterface(vlan10) with sepecific IP 192.168.10.11/24, vlan 10, gateway 192.168.10.1 as management network
subinterface(vlan0) as Edge network
subinterface(vlan100) as vxlan network with IP range 100.100.100.1-3

Or
Let it as default. eg.
eth0 with IP 192.168.10.11/24, vlan 10, gateway 192.168.10.1 as management network
eth0 as edge network
eth0 as vxlan netwokr with IP range100.100.100.1-3

Short Answer:
It depends on whether you need VLAN isolation — but as a best practice, I strongly recommend using VLAN isolation.

Recommended Approach: VLAN Isolation
Create separate sub-interfaces (e.g., eth0.x) for each logical network, each tagged with its respective VLAN ID and IP range as outlined in your setup:
- VLAN 10 – Management
- VLAN 0 – Edge Network
- VLAN 100 – Overlay (VXLAN)
Why VLAN Isolation?
- Network Segmentation – Separates management, storage (VXLAN), and edge traffic
- Security & Performance – Minimizes interference between overlay, management, and user data
- Scalability – Enables independent expansion, migration, or replacement of network segments

Alternative (Not Recommended for Production): Single Interface Setup
Using a single interface (e.g., eth0) for all traffic types — management, edge, and VXLAN — is only suitable for:
- Lab/test environments
- Single-node HCI setups
Drawbacks in Production:
- No traffic isolation — all VLANs are mixed
- Troubleshooting and QoS become more complex
- Performance may suffer under VXLAN-heavy workloads

Physical interface, aggregation port and VXLAN Sub interface need to be set to MTU 1600.