🐛 e2e: fix kubetest to allow parallel execution on different clusters

[chrischdi]

What this PR does / why we need it:

Adjusts the kubetest.Run function to include the cluster name at the reportDir and at the report filename of ginkgo.

This should allow running kubetest.Run in parallel.

As of now one kubetest.Run would e.g. have overwritten the kubeconfig of the other as well as the junit reports, which may also have caused a race condition leading to the flaky dualstack tests (the only e2e prowjobs where we currently run kubetest in-parallel.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/area e2e-testing

[chrischdi]

Related to #8816

[chrischdi]

/test help

[k8s-ci-robot]

@chrischdi: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-cluster-api-build-main
• /test pull-cluster-api-e2e-blocking-main
• /test pull-cluster-api-e2e-conformance-ci-latest-main
• /test pull-cluster-api-e2e-conformance-main
• /test pull-cluster-api-e2e-dualstack-and-ipv6-main
• /test pull-cluster-api-e2e-main
• /test pull-cluster-api-e2e-mink8s-main
• /test pull-cluster-api-e2e-upgrade-1-29-1-30-main
• /test pull-cluster-api-test-main
• /test pull-cluster-api-test-mink8s-main
• /test pull-cluster-api-verify-main

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-apidiff-main

Use /test all to run the following jobs that were automatically triggered:

• pull-cluster-api-apidiff-main
• pull-cluster-api-build-main
• pull-cluster-api-e2e-blocking-main
• pull-cluster-api-test-main
• pull-cluster-api-verify-main

In response to this:

/test help

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.

[chrischdi]

/test pull-cluster-api-e2e-conformance-ci-latest-main
/test pull-cluster-api-e2e-conformance-main
/test pull-cluster-api-e2e-dualstack-and-ipv6-main

[sbueringer]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: aa095996c40f5300537ac2635a4e2e9457cee555

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chrischdi]

/retest

X509 flake

[sbueringer]

Modified PR description to retrigger "PR type" action

[chrischdi]

/cherry-pick release-1.7

[chrischdi]

/cherry-pick release-1.6

[k8s-infra-cherrypick-robot]

@chrischdi: new pull request created: #10426

In response to this:

/cherry-pick release-1.7

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.

[k8s-infra-cherrypick-robot]

@chrischdi: new pull request created: #10427

In response to this:

/cherry-pick release-1.6

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.

[chrischdi]

/cherry-pick release-1.5

[k8s-infra-cherrypick-robot]

@chrischdi: #10424 failed to apply on top of branch "release-1.5":

Applying: test: fix kubetest to allow parallel execution on different clusters
Using index info to reconstruct a base tree...
M	test/e2e/cluster_upgrade.go
M	test/e2e/k8s_conformance.go
M	test/e2e/quick_start_test.go
M	test/framework/kubetest/run.go
Falling back to patching base and 3-way merge...
Auto-merging test/framework/kubetest/run.go
Auto-merging test/e2e/quick_start_test.go
CONFLICT (content): Merge conflict in test/e2e/quick_start_test.go
Auto-merging test/e2e/k8s_conformance.go
CONFLICT (content): Merge conflict in test/e2e/k8s_conformance.go
Auto-merging test/e2e/cluster_upgrade.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 test: fix kubetest to allow parallel execution on different clusters
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.5

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.