Goal: Enable GPU passthrough to a local minikube cluster, install the NVIDIA GPU Operator via Helm, and use kubectl to identify every component the Operator deployed for you automatically — reinforcing the operator pattern before you touch manual MIG/DRA configuration in a later week. Steps:
minikube kubectl -- describe node before moving on.helm repo add nvidia https://nvidia.github.io/gpu-operator
helm repo update
helm install --wait --generate-name \
-n gpu-operator --create-namespace \
nvidia/gpu-operator --version=v26.3.3
kubectl get pods -n gpu-operator -w. Wait until every pod reaches Running/Completed.kubectl get pods -n gpu-operator and, in your own words, identify each pod's role: driver DaemonSet, Container Toolkit, device plugin, GPU Feature Discovery, DCGM Exporter, and node feature discovery components.kubectl describe node <your-node> and record: (a) the automatic GPU-related node labels applied by GPU Feature Discovery/NFD, (b) the nvidia.com/gpu allocatable resource count, and (c) any taints applied to the node.nvidia-smi there directly — do not expect it to run on the host shell:kubectl exec -n gpu-operator -it <nvidia-driver-daemonset-pod> -- nvidia-smi
nvidia.com/gpu: 1 in its resource limits and runs nvidia-smi as its command. Confirm it schedules successfully and prints valid GPU output in its logs (kubectl logs).Deliverables: A short lab report (online text entry or uploaded doc) containing: your kubectl get pods -n gpu-operator output with each pod's role labeled, the relevant kubectl describe node excerpt showing GPU labels/allocatable/taints, the nvidia-smi output from both the driver pod exec and the test pod's logs, and 3–5 sentences reflecting on where nvidia-smi actually lives and why that surprised you (or didn't).