k8s-launch-kit-deploy

Apply generated NVIDIA networking manifests to a Kubernetes cluster in dependency order.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill applies generated NVIDIA networking manifests to a Kubernetes cluster in the correct dependency order, reducing deployment errors and providing validation safeguards before changes are persisted.

Core Features & Use Cases

  • Manifest Deployment: Apply l8k-generated Network Operator, networking, IPAM, policy, and workload resources to a cluster.
  • Helm Integration: Install or upgrade the Network Operator from generated values, including requestor-mode configuration and authenticated chart retrieval.
  • Validation and Safety: Support server-side dry runs, overwrite handling, dependency-aware reconciliation, kubeconfig selection, and post-deployment verification.
  • Use Case: After generating deployment files for an SR-IOV or Spectrum-X environment, use this skill to validate and apply them to a production-like Kubernetes cluster while checking operator readiness and device configuration status.

Quick Start

Use the k8s-launch-kit deploy skill to apply the generated manifests from the deployment directory to the Kubernetes cluster with a server-side dry run first.

Frequently Asked Questions about k8s-launch-kit-deploy

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

FAQPage Schema
How do I deploy NVIDIA networking manifests to a Kubernetes cluster?

To deploy NVIDIA networking manifests to a Kubernetes cluster, apply the generated files in dependency order. This reconciles Network Operators, IPAM, policies, and workloads while validating resources through server-side dry runs before persisting changes.

Can I install the Network Operator using Helm for an SR-IOV environment?

Yes, you can install the Network Operator using Helm by applying generated values. This supports authenticated chart retrieval and requestor-mode configuration tailored for SR-IOV or Spectrum-X environments within your Kubernetes cluster.

What is the best way to validate Kubernetes networking resources before applying them?

The best way to validate Kubernetes networking resources before applying them is using a server-side dry run. This process checks operator readiness, kubeconfig selection, and dependency-aware reconciliation without persisting changes to the cluster.

Do I need specific permissions to apply network operator policies to Kubernetes?

Yes, you need appropriate cluster access and permissions to apply network operator policies. Reconciling operators, networking resources, and device policies requires elevated privileges to ensure successful deployment and post-deployment verification.

How does dependency-aware reconciliation work for Kubernetes cluster operations?

Dependency-aware reconciliation for Kubernetes cluster operations applies generated manifests in the correct order. This reduces deployment errors by ensuring operators, IPAM, and workload resources are sequentially validated and applied before dependent components are processed.

Why are my generated manifests not deploying correctly to the Kubernetes cluster?

Generated manifests may not deploy correctly due to incompatible files, insufficient cluster permissions, or missing dependencies. Ensure you have compatible generated files, valid kubeconfig selection, and appropriate access to reconcile networking resources and device policies.