we currently [use two different versions](https://github.com/kubernetes/kubernetes/pull/117908/commits/356f2deb12403e563a9ecfb400d97f2f5ead35d6#r1620471275) of sample-device-plugin in the node e2e tests.
The reason for this is historical: in https://github.com/kubernetes/kubernetes/pull/115107 we added support to control the registration process to be able to test device failure handling in the application code. Because the invasive changes, we are using two instances of sample device plugins to avoid any chance of unwanted regressions.

In #117908 we are starting to clean up all of this streamlining the handling of sample-device-plugin, which was (apparently?) unnecessarily different than else. The next and final step is to use a single version of sample device plugin for everything. This simple cleanup mostly require careful testing to avoid the aforementioned risk of regressions.
node: e2e: simplify usage of the sample-device-plugin
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : node: e2e: simplify usage of the sample-device-plugin
Issue date:

--- start body ---
we currently [use two different versions](https://github.com/kubernetes/kubernetes/pull/117908/commits/356f2deb12403e563a9ecfb400d97f2f5ead35d6#r1620471275) of sample-device-plugin in the node e2e tests.
The reason for this is historical: in https://github.com/kubernetes/kubernetes/pull/115107 we added support to control the registration process to be able to test device failure handling in the application code. Because the invasive changes, we are using two instances of sample device plugins to avoid any chance of unwanted regressions.

In #117908 we are starting to clean up all of this streamlining the handling of sample-device-plugin, which was (apparently?) unnecessarily different than else. The next and final step is to use a single version of sample device plugin for everything. This simple cleanup mostly require careful testing to avoid the aforementioned risk of regressions.
--- end body ---
