Agent skill · nvidia
cdf-orchestration-setup
Use when the user asks to deploy, install, reinstall, redeploy, upgrade, or connect to the CDF Orchestration Airflow controller. Owns the end-to-end deploy sequence and runs the cdf-orchestration-preflight audit first. Covers make setup, controller image builds, Helm installation, controller connection, port-forwarding, and post-install verification. Not for standalone prerequisite audits or remediation, K3s environments, authoring DAGs, or running workflow payloads.
What it needs
About 9k tokens when loaded.
What this skill does
CDF Orchestration Setup Deploy and verify the Airflow controller after CDF orchestration preflight has established that the checkout and target environment are ready. This skill owns deployment and post-install operations; it does not repeat prerequisite discovery or remediation. Safety boundary Before any Helm install, image push, Airflow connection change, or remote mutation, summarize the exact changes and obtain user approval. Never print kubeconfig, NGC keys, Hugging Face tokens, AWS secrets, OSMO tokens, or Kubernetes Secret bodies. Verify CDF preflight first Before make setup, a controller image build, or any Helm installation or redeployment, invoke and follow $cdf-orchestration-preflight for the same checkout and target environment. Require a fresh preflight report with installreadiness: READY. If installation readiness is BLOCKED or UNVERIFIED, stop and return to preflight to identify and resolve the prerequisite gap. Do not independently rerun prerequisite probes, including local-tool, Kubernetes, GPU, storage/NFS, registry, credential, OSMO, or workflow-mode checks. A WARNING on a tool version means the installed version is outside the tested configuration. It does not block installation: tell the user which tool and version, note that it is untested, and continue once they acknowledge it. runreadiness may still be blocked before the first installation solely because the controller is absent. That is expected and does not block deployment when installreadiness is READY. If preflight identifies K3s, stop. This setup skill does not support or invoke K3s. Carry forward the preflight report's repository root, kubeconfig, namespace, storage class, service mode, and image repository and tag rather than rediscovering them. Preserve the preflight invocation's image and --probe-pod arguments, including any exact --confirmed-push-repository confirmation, for fresh and post-install audits. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/cdf-orchestration-setup