Mellanox Technologies
Official@Mellanox
Mellanox provides Kubernetes networking skills for deploying, configuring, and troubleshooting NVIDIA Network Operator with SR-IOV and RDMA infrastructure.
Agent Skills by Mellanox Technologies
Showing 7 vetted skills indexed across 1 GitHub repositories.
generate-security-md
Generate a SECURITY.md file by analyzing repository code, dependencies, and threat surfaces.
testing-netop-configs
Run and create baseline-diff tests for netop-tools YAML configuration generation.
troubleshooting-network-operator
Diagnose NVIDIA Network Operator failures in Kubernetes clusters using must-gather logs and kubectl checks.
configuring-netop-platform
Configure netop-tools platform settings and network use cases for NVIDIA Network Operator deployments.
upgrading-network-operator
Upgrade NVIDIA Network Operator Helm releases across Kubernetes clusters with rollback support.
deploying-network-operator
Deploy NVIDIA Network Operator on Kubernetes clusters via netop-tools scripts.
managing-netop-devices
Manages SR-IOV virtual functions, PCI devices, link speed, and RDMA tests on Kubernetes nodes.
Frequently Asked Questions About Mellanox Technologies
FAQPage SchemaWhat tasks can I perform with Mellanox's Network Operator skills?▼
You can deploy and upgrade NVIDIA Network Operator on Kubernetes, configure platforms like DGX or OCI with use cases such as sriovnet_rdma or macvlan, manage SR-IOV virtual functions and PCI devices, run RDMA bandwidth tests, and troubleshoot IPAM or NicClusterPolicy failures.
Who should use these netop-tools skills?▼
Platform engineers, cluster administrators, and network operators managing GPU-accelerated Kubernetes clusters with NVIDIA networking hardware. They suit teams running RDMA workloads on DGX, Dell, Lenovo, OCI, or SuperMicro platforms who need repeatable deployment, testing, and diagnostics.
How do I deploy NVIDIA Network Operator using these skills?▼
Use the deploying-network-operator skill to generate Helm values, apply network CRDs, and run ins-network-operator.sh. First configure your platform via configuring-netop-platform by setting global_ops_user.cfg, choosing a use case, selecting IPAM type, and defining the NETOP_NETLIST device list.
How do I validate configuration changes before rollout?▼
Use the testing-netop-configs skill to run unitest.sh, validate YAML generation, create new test cases, and check test baselines. It helps debug test failures and confirms that configuration changes do not break existing netop-tools behavior before applying them to a cluster.
What prerequisites are required to use these skills?▼
A Kubernetes cluster with NVIDIA networking hardware supporting SR-IOV and RDMA is required. You need netop-tools configuration files, Helm for operator installation, and node access for managing VFs, PCI devices, labels, taints, and cordoning during maintenance or upgrades.