e2e testing approach

[seaneagan]

For e2e tests, the Helm Operator and Flux use:

1. bats (testing framework)
2. make e2e (allows running locally, as opposed to github actions only)
3. new kind cluster for each test (test isolation and potentially parallelization)

Are these all still target state for the toolkit components? Or is there an alternate approach planned?

[phillebaba]

Something else that should also be looked at in this case is Flagger as it also supports e2e testing. It would be good to have a standardized method of running tests on deployment that is the same for Helm Controller Kustomize Controller and Flagger.

[seaneagan]

For e2e test isolation and parallelism, could just use github workflow job matrix. This doesn't help with local runs, but maybe that can come later?