Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

$pwd:

k8s-launch-kit-pipeline

Name: K8s Launch Kit Pipeline
Author: NVIDIA

// Use this skill when the user wants to run the full k8s-launch-kit (l8k) pipeline end-to-end: discover cluster hardware, select a profile, generate manifests, and deploy them all in one command. Also activate for CI/CD integration, automation pipelines, 'one-liner', 'complete workflow', or end-to-end NVIDIA networking deployment.

Exécuter dans Manus

$ git log --oneline --stat

stars:11

forks:3

updated:4 mai 2026 à 11:58

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	k8s-launch-kit-pipeline
version	1.1.0
description	Use this skill when the user wants to run the full k8s-launch-kit (l8k) pipeline end-to-end: discover cluster hardware, select a profile, generate manifests, and deploy them all in one command. Also activate for CI/CD integration, automation pipelines, 'one-liner', 'complete workflow', or end-to-end NVIDIA networking deployment.
metadata	{"requires":{"skills":["k8s-launch-kit-shared"]}}

l8k: Full Pipeline

PREREQUISITE: Read ../k8s-launch-kit-shared/SKILL.md for install paths, global flags, and output modes.

Run discovery + generation + deployment as a single command.

Usage

The root command chains all phases in one invocation:

l8k --discover-cluster-config [--kubeconfig <PATH>] \
  --fabric <FABRIC> --deployment-type <TYPE> \
  --save-deployment-files <DIR> --deploy

Or use subcommands for a two-step approach:

l8k discover --save-cluster-config ./cluster-config.yaml && \
l8k generate --user-config ./cluster-config.yaml \
  --fabric <FABRIC> --deployment-type <TYPE> \
  --save-deployment-files <DIR> --deploy

Examples

# Full pipeline: discover + SR-IOV Ethernet + deploy (root command)
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy

# Full pipeline: Spectrum-X
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --spectrum-x RA2.2 --multiplane-mode hwplb --number-of-planes 4 \
  --save-deployment-files ./output --deploy

# Non-default operator namespace
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --network-operator-namespace network-operator \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy

# Agent / CI mode
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy \
  --output json --yes 2>/dev/null

# Pipeline with dry-run (validate everything, apply nothing)
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy --dry-run

# Subcommand alternative: discover then generate+deploy separately
l8k discover --kubeconfig ~/.kube/config \
  --save-cluster-config ./cluster-config.yaml && \
l8k generate --user-config ./cluster-config.yaml \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy

# Skip discovery entirely with --for (known SKU)
l8k generate --user-config ./cluster-config.yaml \
  --for ThinkSystem-SR680a-V3 \
  --node-selector "nvidia.com/gpu.product=NVIDIA-H200" \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy \
  --kubeconfig ~/.kube/config

Common Variations

Use Case	Command
Discovery only	`l8k discover --save-cluster-config <PATH>`
Generate only	`l8k generate --user-config <CONFIG> --fabric ... --save-deployment-files <DIR>`
Generate + deploy	`l8k generate ... --deploy`
Full pipeline (root)	`l8k --discover-cluster-config ... --deploy`
Full pipeline (subcommands)	`l8k discover ... && l8k generate ... --deploy`
Full pipeline dry-run	`l8k --discover-cluster-config ... --deploy --dry-run`

Note: The root command's strength is chaining all phases — it runs discover, generate, and deploy in a single invocation. Use subcommands when you need intermediate inspection or different flags per phase.

Phase Order

Discover — Deploy minimal NicClusterPolicy, read NodeFeature CRDs, group nodes
Generate — Match profile, render templates, write YAMLs
Deploy — Apply resources in dependency order

If any phase fails, subsequent phases are skipped. The JSON output includes which phase failed.

[!CAUTION] The full pipeline includes deployment — confirm with the user before running on production. Use --dry-run to preview first.

Use this skill when the user wants to generate Kubernetes YAML manifests for NVIDIA networking deployment using k8s-launch-kit (l8k). Activate for: manifest generation, profile selection, choosing between SR-IOV/host-device/RDMA-shared/IPoIB/MacVLAN/Spectrum-X, creating deployment files, or when the user asks 'which profile should I use' or needs help choosing a network configuration.

2026-05-0711

k8s-launch-kit-config.md

from "NVIDIA/k8s-launch-kit"

Use this skill when the user needs help understanding, creating, or editing a k8s-launch-kit (l8k) configuration file (l8k-config.yaml or cluster-config.yaml). Activate for: config file questions, parameter tuning, subnet configuration, NV-IPAM setup, DOCA driver settings, NIC configuration operator settings, changing MTU, VFs, resource names, or understanding what any config field does.

2026-05-0711

k8s-launch-kit-discover.md

from "NVIDIA/k8s-launch-kit"

Use this skill when the user wants to discover their Kubernetes cluster's network hardware capabilities using k8s-launch-kit (l8k). Activate for: cluster discovery, hardware detection, NIC detection, finding what GPUs or NICs are in a cluster, creating a cluster config file, or when the user says 'discover' in the context of l8k or NVIDIA networking.

2026-05-0711

k8s-launch-kit-validate.md

from "NVIDIA/k8s-launch-kit"

Use this skill when the user wants to verify that an NVIDIA networking deployment matches the configuration that produced it. Activate for: 'is my deployment correct', 'are all the manifests applied', 'does the network operator version match', 'verify deployment', 'check cluster state against config', or any question about whether the cluster reflects what l8k generated. Wraps the `l8k validate` subcommand.

2026-05-0611

k8s-network-engineer.md

from "NVIDIA/k8s-launch-kit"

Embody a senior NVIDIA Networking Engineer who is an expert on deploying cloud-native networking on Kubernetes with k8s-launch-kit (l8k). Activate whenever the user mentions NVIDIA network profiles, SR-IOV, RDMA, Spectrum-X, BlueField, ConnectX, NIC configuration, Network Operator, DOCA drivers, multirail networking, l8k, k8s-launch-kit, or any Kubernetes networking topic involving NVIDIA hardware. Also activate when the user asks general questions about high-performance networking, GPU interconnect, or RDMA configuration.

2026-05-0611

k8s-launch-kit-deploy.md

from "NVIDIA/k8s-launch-kit"

Use this skill when the user wants to deploy generated NVIDIA networking manifests to a Kubernetes cluster using k8s-launch-kit (l8k). Activate for: applying manifests, deploying to cluster, the `l8k deploy` subcommand or the legacy --deploy flag on `l8k generate`, applying generated files, or any mention of pushing l8k output to a live cluster. Even if the user just says 'apply these' or 'push to cluster' after generating manifests, use this skill.

2026-05-0611

package.json

"author": "NVIDIA"

"repository": "NVIDIA/k8s-launch-kit"

Ouvrir le dépôt GitHub Voir les dépôts du créateur

$ install --global

$ download --local

Exécuter dans Manus

$ useful --forSOC

Administrateurs de réseaux et de systèmes informatiquesProfessions informatiques et mathématiques15-1244L4

name	k8s-launch-kit-pipeline
version	1.1.0
description	Use this skill when the user wants to run the full k8s-launch-kit (l8k) pipeline end-to-end: discover cluster hardware, select a profile, generate manifests, and deploy them all in one command. Also activate for CI/CD integration, automation pipelines, 'one-liner', 'complete workflow', or end-to-end NVIDIA networking deployment.
metadata	{"requires":{"skills":["k8s-launch-kit-shared"]}}

l8k: Full Pipeline

PREREQUISITE: Read ../k8s-launch-kit-shared/SKILL.md for install paths, global flags, and output modes.

Run discovery + generation + deployment as a single command.

Usage

The root command chains all phases in one invocation:

l8k --discover-cluster-config [--kubeconfig <PATH>] \
  --fabric <FABRIC> --deployment-type <TYPE> \
  --save-deployment-files <DIR> --deploy

Or use subcommands for a two-step approach:

l8k discover --save-cluster-config ./cluster-config.yaml && \
l8k generate --user-config ./cluster-config.yaml \
  --fabric <FABRIC> --deployment-type <TYPE> \
  --save-deployment-files <DIR> --deploy

Examples

# Full pipeline: discover + SR-IOV Ethernet + deploy (root command)
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy

# Full pipeline: Spectrum-X
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --spectrum-x RA2.2 --multiplane-mode hwplb --number-of-planes 4 \
  --save-deployment-files ./output --deploy

# Non-default operator namespace
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --network-operator-namespace network-operator \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy

# Agent / CI mode
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy \
  --output json --yes 2>/dev/null

# Pipeline with dry-run (validate everything, apply nothing)
l8k --discover-cluster-config \
  --kubeconfig ~/.kube/config \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy --dry-run

# Subcommand alternative: discover then generate+deploy separately
l8k discover --kubeconfig ~/.kube/config \
  --save-cluster-config ./cluster-config.yaml && \
l8k generate --user-config ./cluster-config.yaml \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy

# Skip discovery entirely with --for (known SKU)
l8k generate --user-config ./cluster-config.yaml \
  --for ThinkSystem-SR680a-V3 \
  --node-selector "nvidia.com/gpu.product=NVIDIA-H200" \
  --fabric ethernet --deployment-type sriov \
  --save-deployment-files ./output --deploy \
  --kubeconfig ~/.kube/config

Common Variations

Use Case	Command
Discovery only	`l8k discover --save-cluster-config <PATH>`
Generate only	`l8k generate --user-config <CONFIG> --fabric ... --save-deployment-files <DIR>`
Generate + deploy	`l8k generate ... --deploy`
Full pipeline (root)	`l8k --discover-cluster-config ... --deploy`
Full pipeline (subcommands)	`l8k discover ... && l8k generate ... --deploy`
Full pipeline dry-run	`l8k --discover-cluster-config ... --deploy --dry-run`

Phase Order

Discover — Deploy minimal NicClusterPolicy, read NodeFeature CRDs, group nodes
Generate — Match profile, render templates, write YAMLs
Deploy — Apply resources in dependency order

If any phase fails, subsequent phases are skipped. The JSON output includes which phase failed.

[!CAUTION] The full pipeline includes deployment — confirm with the user before running on production. Use --dry-run to preview first.

k8s-launch-kit-pipeline

l8k: Full Pipeline

Usage

Examples

Common Variations

Phase Order

See Also

l8k: Full Pipeline

Usage

Examples

Common Variations

Phase Order

See Also

k8s-launch-kit-pipeline

l8k: Full Pipeline

Usage

Examples

Common Variations

Phase Order

See Also

Plus depuis ce dépôt

l8k: Full Pipeline

Usage

Examples

Common Variations

Phase Order

See Also

Plus depuis ce dépôt