nvcf-self-managed-prerequisite
Installation
SKILL.md
NVCA prerequisites — KAI Scheduler + SMB CSI
One operator tool plus two cluster-level components the NVCA operator / compute plane depends on. Satisfy all three before running nvcf-nvca-install.
| Prereq | Why it is needed | Detail |
|---|---|---|
nvcf-cli |
The compute-plane stack's make register-cluster (and install/apply/sync, which abort without the registration values it writes) shells out to nvcf-cli. The shipped stack defaults to building it from a sibling ../cli checkout that the release does not include, so a green-field repo fails with ensure-nvcf-cli / "Registration values not found". |
See Step 0b below |
| KAI Scheduler | selfManaged.featureGateValues includes KAIScheduler; NVCA polls Queue CRs and refuses to become healthy until their quotas are -1 |
references/kai-scheduler.md |
SMB CSI driver (smb.csi.k8s.io) |
NVCA's selfManaged.sharedStorage runs Samba sidecar pods that export file shares; the resulting PVCs need this CSI driver to bind |
references/smb-csi.md |
The KAI Scheduler and SMB CSI installs are cloud-neutral helm commands pinned to NVCF-validated versions. These are upstream third-party charts (not NVCF images), so they are not in manifest.yaml; the per-component reference docs carry the current pin and link the NVCF docs version table. nvcf-cli is an operator workstation tool, not an in-cluster install.
Prerequisites
- A running Kubernetes cluster (any cloud — AKS, EKS, GKE, k3d, MicroK8s) with
kubectlconfigured and admin access. helm>= 3.12 and < 4. Helm 4 is NOT supported (matchesnvcf-self-managed-stack/README.md). On Helm 4 the KAI install below hangs silently for many minutes — Helm 4 runs the chart's pre-installcrd-managerhook through abefore-hook-creationdelete and then waits--timeoutper already-absent hook resource, so the release sits inpending-installwith no pods and never errors cleanly. Use Helm 3.x.- Cluster has CPU headroom on a general-purpose node pool for KAI's 7 pods.