What happened?

deployDevicePlugin leaks the extended resource example.com/resource in node's status.Allocatable/Capacity. This causes conflicts for multiple tests using the extended resource in the same cluster.

What did you expect to happen?

deployDevicePlugin does not leak the example.com/resource in node's status.Allocatable/Capacity, after the test deploying the device plugin completes, the example.com/resource should be cleaned up from node's status.Allocatalbe/Capacity.

How can we reproduce it (as minimally and precisely as possible)?

test/dra/dra.go has tests calling deployDevicePlugin, run the test would be able to reproduce the problem.

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)