fix: keep host-device components in NicClusterPolicy - #224
Conversation
Greptile SummaryThe PR permanently moves host-device OFED and SR-IOV device-plugin configuration into the singleton NicClusterPolicy to avoid overlong DaemonSet names.
Confidence Score: 4/5The PR does not appear safe to merge because merged multirail deployments can still omit valid PCI addresses from SR-IOV resource selectors. The singleton NicClusterPolicy calls legacySriovDevicePluginConfigList, which reads representative PF addresses while merged configurations place the complete address set in RailPciAddresses; nodes using non-representative addresses therefore remain excluded from the expected rail resource. Files Needing Attention: profiles/host-device-rdma/10-nicclusterpolicy.yaml and pkg/networkoperatorplugin/templates.go Important Files Changed
Reviews (3): Last reviewed commit: "fix: keep host-device components in NicC..." | Re-trigger Greptile |
643602c to
d521ed3
Compare
|
Updated the PR scope and force-pushed
Validation is clean: |
Delete the host-device NicNodePolicy template and always render the OFED driver and SR-IOV device plugin through the singleton NicClusterPolicy. This avoids generating an overly long SR-IOV device plugin DaemonSet name. Signed-off-by: Alexander Maslennikov <amaslennikov@nvidia.com>
d521ed3 to
21c9b4b
Compare
|
Corrected the remaining scope gap and force-pushed
Validation is green locally: full tests, build, golangci-lint, and |
Summary
profiles/host-device-rdma/11-nicnodepolicy.yamland remove it from the host-device profileNicClusterPolicyThis avoids Network Operator deriving an overlong SR-IOV device-plugin DaemonSet name from a host-device
NicNodePolicy. Support can be enabled again with Network Operator 26.10.Testing
CGO_ENABLED=0 go test ./... -count=1CGO_ENABLED=0 go build ./...CGO_ENABLED=0 go run github.com/golangci/golangci-lint/v2/cmd/golangci-lint@v2.11.0 run ./...git diff --check