-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
None
-
None
-
None
Having to wait for e2e and e2e-pool to run in the CI env, and attempting to debug therein, can be inconvenient and slow. However, running those tests "locally" requires nontrivial setup.
Create some kind of make target, wrapper script (see hack/local-e2e-test.sh for a start?), or whatever for both tests to make it as easy as possible to run them "locally" (in the same sense that make deploy runs "locally" – against whatever target cluster my kubeconfig is pointing to).