Add support for GDRCOPY

[elezar]

This change adds support for GDRCOPY through the same mechansim as for GDS and MOFED. This requires new functionality in the nvidia-container-toolkit to generated CDI specs for gdrcopy devices when using CDI mode.

This depends on NVIDIA/nvidia-container-toolkit#1230

[Copilot]

Pull Request Overview

This PR adds support for GDRCOPY functionality to the NVIDIA Kubernetes device plugin, following the same pattern as existing GDS and MOFED support. GDRCOPY enables GPU Direct Remote Direct Memory Access (RDMA) Copy functionality for high-performance GPU-to-GPU communication.

• Adds GDRCOPY configuration option with environment variable support
• Integrates GDRCOPY into the CDI (Container Device Interface) specification generation
• Updates dependencies to support the new GDRCOPY functionality in nvidia-container-toolkit

Reviewed Changes

Copilot reviewed 12 out of 138 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
internal/plugin/server.go	Sets NVIDIA_GDRCOPY environment variable when GDRCOPY is enabled
internal/cdi/options.go	Adds WithGdrcopyEnabled option for CDI handler configuration
internal/cdi/imex.go	Updates interface signatures for compatibility with nvidia-container-toolkit
internal/cdi/cdi.go	Integrates GDRCOPY into CDI spec generation alongside GDS/MOFED
internal/cdi/api.go	Removes local cdiSpecGenerator interface, uses upstream interface
go.mod	Updates nvidia-container-toolkit and CDI dependencies to support GDRCOPY
deployments/helm/nvidia-device-plugin/values.yaml	Adds gdrcopyEnabled helm configuration option
deployments/helm/nvidia-device-plugin/templates/daemonset-device-plugin.yml	Adds GDRCOPY_ENABLED environment variable to daemonset
cmd/nvidia-device-plugin/plugin-manager.go	Passes GDRCOPY configuration to CDI handler
cmd/nvidia-device-plugin/main.go	Adds gdrcopy-enabled CLI flag
api/config/v1/flags_test.go	Updates test expectations for new GDRCOPY flag
api/config/v1/flags.go	Adds GDRCopyEnabled field to configuration structure

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}

[Copilot]

The comment incorrectly mentions 'GDS' instead of 'GDRCOPY'. It should read 'provides an option to set whether a GDRCOPY CDI spec should be generated'.

Suggested change

	// WithGdrcopyEnabled provides and option to set whether a GDS CDI spec should be generated
	// WithGdrcopyEnabled provides an option to set whether a GDRCOPY CDI spec should be generated

[cdesiniotis]

+1

[cdesiniotis]

Some minor comments. LGTM otherwise.

[cdesiniotis]

Question -- since the NVIDIA_GDRCOPY=enabled envvar only gets set when a non-CDI device list strategy is configured, would it make sense to omit this implementation detail from the usage string? What about a more generic usage string, like "ensure that containers get access to the GDRCopy device nodes". This comment also applies to the gds-enabled and mofed-enabled flags.

[cdesiniotis]

+1