Repository navigation
Conversation
…gmExporter.env The localhost check for DCGM running on the host reads DCGM_REMOTE_HOSTENGINE_INFO from the container before the user env is applied, so the value from dcgmExporter.env is never seen and the exporter stays on the pod network. Check after the user env instead. Signed-off-by: Youssef Omar Bouden <youssef.bouden2002@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Priority: ➖ Normal Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to
|
Description
When
dcgm.enabledis false, the exporter needshostNetworkto reach a DCGM host engine onlocalhost. The check readDCGM_REMOTE_HOSTENGINE_INFOfrom the container beforedcgmExporter.envwas applied, so a value set there was never seen. 54c270c moved the user env to the end ofTransformDCGMExporterand left the check where it was.The check now runs after the user env loop. The
nvidia-dcgm:5555default for an operator-managed DCGM stays where it is, so a user value still overrides it.Fixes #3091
Checklist
make lint) (rangolangci-lint run ./controllers/...: 0 issues, andgofmt -s -l controllers/: clean)make validate-generated-assets) (not run; no API or generated files changed)make validate-modules) (not run; no dependency changes)Testing
New case "transform dcgm exporter with dcgm running on the host set only through dcgmExporter env" in
TestTransformDCGMExportersupplies the variable only through the ClusterPolicy. It fails on main and passes with this change.go test ./controllers/passes (Go 1.27.2, macOS arm64). Not tested on a cluster.