kubernetes/test/e2e/framework/pod
Clayton Coleman 286d989d8d
test/e2e: Allow test invokers to skip test waits before and after
A number of e2e tests are useful to run after the system has been
disrupted or is in the progress of being disrupted, but the current
suite and test logic blocks progress waiting for all nodes to be
healthy.

By passing -1 to --minStartupPods or --allowed-not-ready-nodes flags
the caller can bypass wait logic before and after test suites that
would prevent running e2e during disruption. This allows use of parts
of the e2e suite during cluster duress to verify that controllers or
components still function.
2021-02-04 20:14:05 -05:00
..
BUILD Run hack/update-vendor.sh 2020-05-16 07:54:33 -04:00
create.go FsgroupChange policy test suite 2020-11-10 08:36:07 +00:00
delete.go Revert "e2epod: use foreground deletion" 2020-07-21 22:40:31 +03:00
node_selection.go e2e: avoid setting NodeName for CSI driver deployments 2020-02-26 10:33:29 +01:00
resource_test.go Fix a bug in e2epod function 2020-02-13 16:45:16 -08:00
resource.go Merge pull request #95065 from JornShen/replace_restarting_kas_kp_e2e_network_provider 2020-11-03 17:04:03 -08:00
wait.go test/e2e: Allow test invokers to skip test waits before and after 2021-02-04 20:14:05 -05:00