When bootstrapping a Kubernetes cluster for accelerated AI workloads using the NVIDIA GPU Operator, which three core components are deployed as absolute prerequisites to establish basic GPU scheduling and containerized access?
Select all correct answers, then click Submit.
Short Explanation and Infographic
Think of setting up GPUs in Kubernetes like building a high-performance sports car. You need the engine, the transmission, and the driver. In our world, that's the GPU Driver to let the OS talk to the hardware, the Container Toolkit to make sure your containers can actually leverage those CUDA cores, and the Device Plugin so Kubernetes knows the GPUs even exist and can schedule workloads on them. The other stuff like DCGM for telemetry, MIG for slicing up your GPUs, or GPUDirect Storage for bypass operations? Those are awesome upgrades, but you don't need them just to get the car out of the driveway. Make sure you know these three core components for the exam!
Full explanation below image
Full Explanation
The NVIDIA GPU Operator simplifies the lifecycle management of NVIDIA GPUs in Kubernetes clusters by automating the deployment and management of all the necessary software stack components. To run basic GPU workloads in Kubernetes, three foundational components must be installed and active: 1. NVIDIA GPU Driver: Installed via a containerized driver package, this component acts as the kernel-space interface to the hardware. Without it, the operating system cannot communicate with the physical GPU accelerators, making it the most critical prerequisite. 2. NVIDIA Container Toolkit: This component modifies the container runtime configuration (such as containerd, CRI-O, or Docker) by registering the NVIDIA container runtime. This allows containers to access the underlying GPU hardware resources and run CUDA-based operations by dynamically injecting driver libraries. 3. NVIDIA Device Plugin: Running as a DaemonSet, this plugin registers the available GPUs as allocatable resources within the Kubernetes scheduler. It monitors GPU availability and reports it to the kubelet, enabling developers to request GPUs in pod specifications using syntax like nvidia.com/gpu.
Conversely, the remaining distractors represent advanced, optional additions: - NVIDIA Data Center GPU Manager (DCGM) is a suite of tools for monitoring and managing GPUs in cluster environments. It collects telemetry and health metrics, which is crucial for monitoring stack integrations (like Prometheus/Grafana) but is not required to run workloads. - NVIDIA Multi-Instance GPU (MIG) Manager is used to dynamically configure MIG profiles to slice a physical GPU into multiple independent instances. This is an advanced optimization for multi-tenant efficiency. - NVIDIA GPUDirect Storage (GDS) establishes a direct DMA path between storage (like NVMe) and GPU memory, bypassing CPU bounce buffers. It is a performance-oriented storage optimization rather than a basic system dependency.