feat(metadata-augmentor): include Topograph topology labels by default#1226
Conversation
Append the four topology labels written by NVIDIA/topograph to the Metadata Augmentor's default `allowedLabels`: - network.topology.nvidia.com/accelerator - network.topology.nvidia.com/leaf - network.topology.nvidia.com/spine - network.topology.nvidia.com/core On clusters where Topograph is deployed, these labels describe the physical network topology (NVLink domains, leaf/spine/core switch hierarchy). With them allowed, NVSentinel propagates them into health event metadata so downstream consumers (CEL rules, remediation CRs, dashboards, blast-radius analysis) can reason about topological locality. On clusters without Topograph the labels are absent and the Metadata Augmentor skips them — no operator-side configuration change. Also add a Topograph-labels test case to the transformer suite (mirrors the existing cloud-specific topology labels case) and a short "Topology Awareness (Topograph)" section to docs/INTEGRATIONS.md.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughNVSentinel's metadata enrichment configuration is extended to recognize four Topograph-emitted network topology labels ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 golangci-lint (2.11.4)level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies" Comment |
|
cc @dmitsh — FYI |
Summary
Include the four node labels written by NVIDIA/topograph in the Metadata Augmentor's default
allowedLabels:network.topology.nvidia.com/accelerator— NVLink domain (clique) IDnetwork.topology.nvidia.com/leaf,/spine,/core— switch hierarchy levelsWhen Topograph is deployed, these labels describe the cluster's physical network topology. With them allowed by default, NVSentinel propagates them into health event metadata so downstream consumers (CEL rules, remediation CRs, dashboards, blast-radius analysis) can reason about topological locality without operator-side configuration.
Implements Option 1 (default-on in Metadata Augmentor) from #1205, per @XRFXLP's and @lalitadithya's guidance.
On clusters without Topograph the labels are absent and the Metadata Augmentor simply skips them — no behavior change there.
Type of Change
Component(s) Affected
docs/INTEGRATIONS.md)Testing
helm templateagainst bothdistros/kubernetes/nvsentinel/values.yamlandvalues-full.yaml— confirms the four keys render into the platform-connectors ConfigMap'sallowedLabelshelm lint distros/kubernetes/nvsentinel— no new findingsgo test ./platform-connectors/pkg/transformers/metadata/...passes on Go 1.26.2, including a newtopograph topology labelstest case that mirrors the existingcloud-specific topology labelscaseChecklist
docs/INTEGRATIONS.md; topograph labels also added inline (with comment + link) in both default values filesRelated
Summary by CodeRabbit
New Features
Documentation
Tests