Start Envtest processes in parallel

[crew-helper]

Hi.

We use envtest to write integration tests and it looks great, very easy, and fast to start!
Though our resource takes considerable time to start as it waits for the external providers and update/create may take around 10 minutes. So with growing amount of tests we'll end up in long running time for the integration tests.

I sought ways to parallize this and as with ginkgo this looks quite simple as just ginkgo -p makes all the parallelization though this results in BeforeSuite run in parallel and envtest fails as apiServers don't start. I thought about setting the different ports for ApiServer and different data directories for etcd but the ControlPlane struct is in controller-runtime/pkg/internal/testing/integration so it's not available from external code.

Questions: is it possible to start envtest environments in parallel? If not - is it something planned to be done?

thanks!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nilsherzig]

Hi @crew-helper I'm stuck at the exact same spot you're describing, did you find a solution for this problem?