k8s-launch-kit-dryrun
作成者: nvidia
このスキルは、ユーザーがk8s-launch-kit(l8k)で何がデプロイされるかを変更せずにプレビューしたい場合や、設定を安全に検証したい場合に使用します…
npx skills add https://github.com/nvidia/k8s-launch-kit --skill k8s-launch-kit-dryrunl8k: Dry Run & Validation
PREREQUISITE: Read
../k8s-launch-kit-shared/SKILL.mdfor install paths, global flags, and output modes.
Preview what l8k would deploy without making cluster changes, or validate a configuration.
Usage
# Generate-only (no --deploy, no cluster changes)
l8k generate --user-config <CONFIG> --fabric <FABRIC> --deployment-type <TYPE> \
--save-deployment-files <DIR>
# Dry-run with deploy flag (validates against live cluster but doesn't apply)
l8k generate --user-config <CONFIG> --fabric <FABRIC> --deployment-type <TYPE> \
--save-deployment-files <DIR> --deploy --dry-run [--kubeconfig <PATH>]
Modes
| Mode | Flags | Cluster Access | What It Does |
|---|---|---|---|
| Generate-only | No --deploy | Not needed | Renders templates, writes YAMLs to disk |
| Dry-run | --deploy --dry-run | Needed | Generates + validates against cluster, doesn't apply |
Examples
# Preview generated files (no cluster needed)
l8k generate --user-config cluster-config.yaml \
--fabric ethernet --deployment-type sriov \
--save-deployment-files ./output
# Dry-run against live cluster
l8k generate --user-config cluster-config.yaml \
--fabric ethernet --deployment-type sriov \
--save-deployment-files ./output \
--deploy --kubeconfig ~/.kube/config --dry-run
# Agent mode: get manifest list as JSON
l8k generate --user-config cluster-config.yaml \
--fabric ethernet --deployment-type sriov \
--save-deployment-files ./output \
--deploy --dry-run --kubeconfig ~/.kube/config \
--output json --yes 2>/dev/null
# Schema discovery (list capabilities)
l8k schema
JSON Output (Dry-Run)
{
"success": true,
"phase": "generate",
"profile": {"fabric": "ethernet", "deploymentType": "sriov"},
"generatedFiles": ["output/group-0/nicclusterpolicy.yaml", "..."],
"deployed": false,
"dryRun": true
}
Tips
- Generate-only is the safest starting point — inspect the YAMLs before applying.
- Use
l8k schemato programmatically discover available profiles and flags. - Combine
--dry-run --output jsonfor CI validation gates.
See Also
- k8s-launch-kit-shared — Global flags and exit codes
- k8s-launch-kit-deploy — Apply after previewing