
Some node e2e tests check for expected number of pods running on the node to verify the correct state of that node after running test scenarios. An example of such a check is in the device plugin end to end test here: [1]. If the node is not left in a clean state after an e2e test finishes running, it can lead to flaky tests because the node might have unexpected pods running on the node. In order to avoid that, we make sure that the test pods are cleaned up after the test runs. [1]: https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/device_plugin_test.go#L189-L190 Signed-off-by: Swati Sehgal <swsehgal@redhat.com>