k8s-launch-kit-discover

Discover Kubernetes cluster networking hardware and generate a resolved cluster-config.yaml.

14|5|Updated Nov 4, 2025
One-click install
npx skills add https://github.com/NVIDIA/k8s-launch-kit --skill k8s-launch-kit-discover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-launch-kit-discover
Source: https://github.com/NVIDIA/k8s-launch-kit/tree/main/skills/k8s-launch-kit-discover
Command: npx skills add https://github.com/NVIDIA/k8s-launch-kit --skill k8s-launch-kit-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the manual effort and guesswork involved in identifying Kubernetes cluster networking hardware, GPUs, NICs, rails, node groups, and deployment profile settings.

Core Features & Use Cases

  • Self-contained cluster discovery: Bootstraps the NIC Configuration Daemon in a private namespace without requiring a pre-installed Network Operator.
  • Hardware and topology detection: Discovers NVIDIA NICs, GPUs, east-west rails, north-south devices, node groups, OFED-dependent modules, and applicable topology presets.
  • Configuration generation: Produces a reusable cluster-config.yaml with resolved profile values, node selectors, hardware groups, and preserved documentation comments.
  • Use Case: Use it to inspect a new NVIDIA Kubernetes cluster, determine whether SR-IOV, RDMA shared, or host-device deployment is appropriate, and save the resulting configuration for manifest generation.

Quick Start

Ask the AI to discover the Kubernetes cluster hardware and save the resolved configuration to the specified cluster-config.yaml path.

Frequently Asked Questions about k8s-launch-kit-discover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover Kubernetes NICs and GPU topology in an NVIDIA cluster?

You can discover Kubernetes NICs and GPU topology by bootstrapping the NIC Configuration Daemon in a private namespace to detect NVIDIA networking hardware, east-west rails, and node groups, generating a resolved cluster configuration file.

Do I need a pre-installed Network Operator for Kubernetes cluster discovery?

No, Kubernetes cluster discovery does not require a pre-installed Network Operator because the process bootstraps the NIC Configuration Daemon independently in a private namespace using Kubernetes API access.

How do I generate a cluster-config.yaml with resolved RDMA and SR-IOV profiles?

To generate a cluster-config.yaml with resolved RDMA and SR-IOV profiles, the discovery process detects applicable deployment presets, hardware groups, and node selectors while preserving your existing configuration comments.

Can I detect OFED-dependent modules and north-south devices in a Kubernetes cluster?

Yes, you can detect OFED-dependent modules and north-south devices during cluster discovery, which identifies NVIDIA NICs, GPUs, and fabric topology to determine appropriate deployment profiles.

Does Kubernetes hardware discovery preserve my existing configuration and CLI overrides?

Yes, Kubernetes hardware discovery preserves your existing user configuration and applies explicit CLI overrides directly into the final resolved cluster configuration file output.

What Kubernetes access is required to detect NVIDIA networking hardware and rails?

Detecting NVIDIA networking hardware and rails requires Kubernetes API access, an accessible NIC Configuration Daemon image, and optional image-pull secrets to successfully resolve the cluster topology.