You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
demos: drop daemon-mode cuda check in favor of preflight-checks/cuda-validation
The demo re-bundled CUDA context/memory validation as a polling daemon
check — the exact model deesharma24 rejected on #891, where a long-running
daemon contends for GPU memory with active workloads. That review is why
CUDA validation re-landed as a preflight init-container (#1384), which runs
once before workloads schedule.
Remove the daemon check from this demo to avoid contradicting the accepted
design: delete checks/cuda_validation.py and drop all references from
monitor.py, config.py, metrics.py, the k8s ConfigMap/PrometheusRule, and the
tests. README now points at preflight-checks/cuda-validation/ (#1384) as the
supported form.
Also note in the DaemonSet that the system-services-monitor:0.1.0 tag is a
demo-local pin, independent of the Helm chart appVersion.
> **CUDA validation is not part of this monitor.** Polling CUDA context/memory tests from a long-running daemon contends for GPU memory with active workloads (see the [#891 review](https://github.com/NVIDIA/NVSentinel/pull/891)). The supported form is a preflight init-container that runs once before workloads schedule — see [`preflight-checks/cuda-validation/`](../../preflight-checks/cuda-validation/) (#1384).
21
22
22
23
## Quick Start
23
24
@@ -60,7 +61,6 @@ The ServiceMonitor includes PrometheusRule with alerts:
0 commit comments