What problem does it solve? Whole-GPU allocation in Kubernetes leaves expensive NVIDIA GPUs mostly idle when workloads are small or bursty, and teams lack a clear method for choosing between MIG, MPS, and time-slicing or producing the correct device plugin configuration. ## Core Features & Use Cases - Sharing technique selection: Compares MIG, MPS, and time-slicing across isolation, fault tolerance, overhead, and hardware support, with decision rules per workload pattern. - Utilization waste analysis: Computes memory and compute waste from DCGM metrics (DCGM_FI_DEV_GPU_UTIL, DCGM_FI_DEV_FB_USED) to justify sharing before recommending anything. - Concrete configuration output: Produces NVIDIA GPU Operator MIG strategies (single vs mixed) and time-slicing ConfigMaps with replica counts sized from model footprints. - Use Case: A research cluster has ten replicas of a distilled 1B model each reserving a whole 24 GB L4. The skill quantifies the 92% memory waste, recommends time-slicing with 10 replicas, and outputs the ConfigMap plus verification commands. ## Quick Start Ask the assistant to evaluate whether your GPU workloads should use MIG, MPS, or time-slicing and to generate the NVIDIA device plugin configuration for your cluster.