k8s-launch-kit-config

Kubernetes network configuration for SR-IOV and RDMA is managed by editing deployment profile files to define virtual functions, resource names, and host-device settings. The configuration process preserves discovered hardware data while applying these network operator parameters safely.

NV-IPAM is an IP address management configuration within Kubernetes network deployments that allows you to manually define custom subnets. It integrates with network operator settings to allocate IP ranges across discovered hardware groups during cluster topology configuration.

To enable jumbo frames, you adjust the MTU parameter in your Kubernetes network configuration file to 9000. This NIC configuration change is applied alongside SR-IOV and RDMA settings while ensuring write-back preservation of existing hardware discovery data.

Yes, Kubernetes network configurations support Spectrum-X options and topology presets for hardware groups. You can apply exact topology matching and cluster selectors to ensure your deployment profile aligns precisely with your discovered hardware topology.

Maintenance concurrency is controlled by specifying the number of concurrent operations in your Kubernetes network configuration file. You can set parameters like four concurrent maintenance operations while preserving existing hardware discovery data and configuration precedence rules.

Editing Kubernetes network configurations for DOCA drivers requires adherence to configuration precedence and field-level defaults. Limitations include the need for exact topology matching and safe manifest-generation to avoid overwriting resolved hardware settings during write-back operations.