🐛 test/e2e/cluster-upgrade: skip worker upgrades if worker count is 0

[sbueringer]

Signed-off-by: Stefan Büringer buringerst@vmware.com

What this PR does / why we need it:
Currently, the cluster upgrade test fails when the worker count is 0 (#4896 (comment)). This PR makes sure we skip the upgrade of MachineDeployments and MachinePools in that case.

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 #

[sbueringer]

/test pull-cluster-api-verify-main

[fabriziopandini]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

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:

• test/OWNERS [fabriziopandini]

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

[CecileRobertMichon]

Thank you @sbueringer for the super fast fix

[CecileRobertMichon]

@fabriziopandini do we need to backport this to include it in release 1.1 since the beta release tag already exists or will everything in main be included?

[sbueringer]

@fabriziopandini do we need to backport this to include it in release 1.1 since the beta release tag already exists or will everything in main be included?

I think we don't. I expect the release to be cut from current main as there is no release-1.1 branch yet and I think it will be created from main at the time of the release. But let's see what Fabrizio says of course :)

[fabriziopandini]

the 1.1 branch does not exist yet, it will be created when we cut the release; it makes sense to cut an rc to allow providers to get this before the release (we should get a couple of PR in before...)