🐛 E2E: Do not require kubetest configration if not needed

[vknabel]

What this PR does / why we need it:
Currently e2e.ClusterUpgradeConformanceSpec always requires an existing KUBETEST_CONFIGURATION file path even if SkipConformanceTests is true.
This PR adds a condition to skip these Expects.

In the testing pipeline for our infrastructure provider we rely on sonobuoy instead of kubetest and therefore don't even need a kubetest config.

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: vknabel / name: Valentin Knabel (4759d95)

[k8s-ci-robot]

Welcome @vknabel!

It looks like this is your first PR to kubernetes-sigs/cluster-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign fabriziopandini for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @vknabel. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[chrischdi]

/ok-to-test

@vknabel you will need to solve the CLA issue.

[vknabel]

@chrischdi thx for having a look.
The CLA agreement is in internal progress at my company. It should be signed on monday.

[sbueringer]

/test pull-cluster-api-e2e-main-gke

[vknabel]

FYI solved the CLA issue (though it required a push to trigger the CLA hook after signing)