Sam Dowell

/retest

/ok-to-test

Hi @tomasaschan, I put together a [public design doc](https://docs.google.com/document/d/1QK-vMQkcjmgKqaqI7fBBpejwr2eJsWu7lzO1q3PQqe4) which puts forth a proposal to solve this problem. Please feel free to comment/review.

@tomasaschan Added you as a commenter on the doc. Would you mind copying your comment there so we can discuss in a thread?

SGTM, let's profile test runs on this PR. Perhaps we can create another PR with no changes as a baseline comparison?

/hold

> > Perhaps we can create another PR with no changes as a baseline comparison? > > We can compare the performance based on the presubmit job history: https://oss.gprow.dev/job-history/gs/oss-prow-build-kpt-config-sync/pr-logs/directory/kpt-config-sync-presubmit-e2e-multi-repo @haiyanmeng...

@haiyanmeng I suspect the second optional is the viable option if we really want to start pushing the scale of the test parallelism. My only concern is that we are...

My understanding is that `e2e.sh` and `setup.sh` is test scaffolding specifically for the bats tests. The go e2e tests use [this script](https://github.com/GoogleContainerTools/kpt-config-sync/blob/main/build/test-e2e-go/e2e.sh) as an entry point and the kind clusters...

I think we should turn off the bats prow jobs before removing all of this, otherwise this will be a breaking change