k8s-launch-kit-shared

l8k — Shared Reference

Source Development and Installation

For source changes, read the checkout's AGENTS.md and the applicable extension contracts. Their scenarios guide integration verification; their baseline exceptions identify existing limits. Update shared contracts when their promises change, and affected docs/skills with behavior changes. Routine conforming additions need no separate spec. Build and test that checkout from its repository root:

make build
./build/l8k schema

Global installation is optional for development. When installation is requested, make install copies the binary and assets, while make dev-install links assets into the source tree. Both use scripts/install-local.sh, can download supporting assets and can write system paths; inspect the targets first.

Install Paths

After installation, l8k is available system-wide. Default configuration and topology presets are embedded; existing filesystem overrides are preserved.

Binary Discovery (for AI agents)

For installed CLI workflows, use command -v l8k. If it is unavailable, report the missing prerequisite and use the installation guidance above when installation is within the user's request. For source development, use ./build/l8k after make build; do not substitute an unrelated installed binary for the checkout being tested.

Available Commands

The root command l8k --discover-cluster-config ... still works for backward-compatible full-pipeline usage.

Target selection

discover, generate, deploy, validate, and the root pipeline default to the host target. Existing invocations must omit --target unless the user explicitly requests it; --target host is an equivalent explicit form.

The dpf target name is reserved but its phases are not implemented in this build. Do not attempt DPF provisioning. Use l8k schema and inspect targets[].phases before selecting any non-host target. Host-only flags such as --fabric, --kubeconfig, and the Network Operator/Spectrum-X flags are rejected when explicitly combined with another target.

Internally, each lifecycle command snapshots the explicitly supplied Host arguments, binds a phase-specific adapter through the target registry, and runs the resulting operation exactly once with the command context. Do not bypass this route when extending or automating a lifecycle phase. The canonical component and data-flow diagrams live in docs/architecture/overview.md; update them with any change to lifecycle, package ownership, artifacts, or external integration boundaries.

Common Flags And Command Scope

Use command help for applicability; these are not all inherited flags. The complete matrix is in docs/reference/cli.md. --yes and --quiet are root-only, --deploy-timeout belongs to root/standalone deploy, and --overwrite-existing belongs to generate/standalone deploy.

Common Flag Reference

The persistent networkOperator.skipHelmChart setting also makes l8k clean retain the externally owned Helm release while deleting Network Operator custom resources. Clean does not route the skip flag; use config for the ownership policy or --keep-helm-chart for an explicit retention-only override.

l8k discover and l8k generate both accept the profile flags --fabric, --deployment-type, --multirail, --spectrum-x, --multiplane-mode, and --number-of-planes. Discovery persists the resolved values; later generation reuses them unless another explicit CLI override is supplied.

For automation, l8k schema exposes configPaths on config-backed flags. The metadata comes from the shared option bindings used during resolution, so use it instead of maintaining a separate CLI-to-YAML mapping.

Agent / JSON Mode

Use --output json for lifecycle commands. Root/discover/generate produce a single result envelope; clean produces a cleanup result. Standalone deploy has no finalized success envelope: use its exit status. Validate emits a stream of result objects, including a separate reportPath object when written. schema and version --output json each return one object. Preset commands and sosreport emit text on success even with the inherited output flag.

Do not pass --yes to subcommands; it is root-only. Lifecycle JSON mode already auto-confirms prompts; keep the operation within the user's existing authorization. Text/help/schema inspection is appropriate when testing those interfaces. Preserve stderr as diagnostic evidence. Capture status before parsing instead of letting a successful jq mask a failing command:

status=0
l8k validate --deployment-files ./deployment --output json \
  >validation.jsonl 2>validation.log || status=$?
jq -s . validation.jsonl
exit "$status"

summary.success in validation's manifest object is not the final acceptance verdict. Check the process status, report, skipped stages, and required test coverage. Full Kubernetes validation can succeed with incomplete connectivity; connectivity-only and OpenShift runs enforce selected-family coverage. See docs/integrator/automation.md and docs/user/validation.md for the contracts.

Exit Codes

Structured Error Output (JSON mode)

{
  "success": false,
  "phase": "discover",
  "deployed": false,
  "error": {
    "code": "CLUSTER_ERROR",
    "message": "cluster discovery failed",
    "category": "cluster",
    "transient": true,
    "suggestion": "Check that kubeconfig is valid and the cluster is reachable"
  },
  "messages": [...]
}

Error categories: validation, cluster, deployment. The transient field hints whether retrying might help.

Schema Discovery

# List all l8k capabilities as JSON
l8k schema

Use l8k schema to programmatically discover available profiles, fabrics, deployment types, flags, exit codes, and output formats.

Security Rules

• Verify the target/context and stay within the user's existing authorization for live changes. A skill does not grant deployment or cleanup authority.
• Use deployment dry-run to preview changes where supported. Discovery and connectivity checks create cluster resources; root pipeline --dry-run does not make every phase read-only. clean has no dry-run mode.
• Never expose credentials or kubeconfig contents in output.

Maintaining This Guidance

When behavior changes, update the affected documentation sections, phase skills and bundled references in the same PR. Follow the documentation requirements, check examples against schema/help, and keep shared rules here.

Network Operator Namespace Resolution

Applies to l8k generate / l8k deploy / l8k validate only. l8k discover manages its own private namespace (nvidia-k8s-launch-kit) and ignores this flag.

Both nvidia-network-operator and network-operator are common default namespaces for an existing Network Operator install. If l8k generate / l8k deploy / l8k validate can't find Network Operator resources, retry with --network-operator-namespace <correct-namespace>.

OpenShift

Use --flavor ocp or flavor: ocp for OpenShift Host workflows. The default is k8s. See docs/user/openshift.md for external operator prerequisites and namespace defaults.