Deployment Profiles
On this page
A profile is a named combination of fabric and deployment type. Each profile maps to a complete set of Kubernetes manifests produced by l8k generate. Pick a profile from the decision tree or table below, then follow the link.
For the conceptual difference between fabric and deployment type, see Overview.
Decision Tree
Fabric is determined by the underlying hardware topology (Spectrum-X clusters are detected as a distinct fabric, not as a flavour of Ethernet). Pick the deployment type for each fabric:
Decision Matrix
Profile |
When to use |
Fabric / Deployment type |
Keywords |
|---|---|---|---|
High-performance Ethernet networking with hardware acceleration. Per-pod dedicated VFs. |
ethernet / sriov |
SR-IOV, RDMA, low-latency, dedicated VFs |
|
Virtualized InfiniBand with hardware acceleration. Isolated IB partitions per pod. |
infiniband / sriov |
SR-IOV, InfiniBand, large-scale HPC |
|
Direct hardware passthrough. Minimal CPU overhead. Exclusive device access per pod. |
ethernet or infiniband / host_device |
host-device, PCI-passthrough, DPDK |
|
InfiniBand networking with shared RDMA resources. Parallel I/O workloads. |
infiniband / rdma_shared |
IPoIB, shared-device, high-bandwidth |
|
Multi-tenant Ethernet with shared RDMA capabilities and network isolation. |
ethernet / rdma_shared |
MacVLAN, multi-tenant, network-segmentation |
|
NVIDIA Spectrum-X multi-rail AI interconnect (RA2.1 or RA2.2). HWPLB / SWPLB / Uniplane / None modes. |
ethernet / sriov / spectrum-x |
Spectrum-X, multiplane, RA2.2, HWPLB |
See Also
Overview — profile selection vocabulary
Generate Workflow — how profile flags are consumed
Heterogeneous Clusters — mixing profiles per node group