k8s-launch-kit-dryrun
Skill18 starsChanged 48 days agoApache-2.0View on GitHub
Use this skill when the user wants to preview what k8s-launch-kit (l8k) would deploy without making changes, or wants to safely validate their configuration before applying. Activate for: dry-run, preview, validation, 'what would happen if', testing configurations, schema discovery, checking generated manifests, or any cautious pre-deployment step. Also use when the user asks 'is my config valid' or 'show me what would be created' -- even without mentioning dry-run explicitly.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- k8s-launch-kit-cleanSkill
- k8s-launch-kit-configSkill
- k8s-launch-kit-deploySkill
- k8s-launch-kit-discoverSkill
- k8s-launch-kit-generateSkill
- k8s-launch-kit-pipelineSkill
- k8s-launch-kit-sharedSkill
- k8s-launch-kit-troubleshootSkill
- k8s-launch-kit-validateSkill
- k8s-network-engineerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 76
Use l8k schema to programmatically discover available profiles and flags.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
l8k: 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
# Schema discovery (list capabilities)
l8k schemaJSON Output (Dry-Run)
{
"success": true,
"phase": "generate",
"profile": {"fabric": "ethernet", "deployment": "sriov"},
"generatedFiles": ["output/network-operator/10-nicclusterpolicy.yaml", "output/.l8k/resolved-config.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
OpenShift
For OpenShift, use --flavor ocp; NV-IPAM IPPool validation may be deferred because its CRD appears only after live NCP reconciliation. A deferred check is not a pass.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

