🌱 [e2e] Checks unexpected rollouts during clusterctl upgrade

[ykakarap]

What this PR does / why we need it:

Check for unexpected rollouts in the clusterctl upgrade e2e test.

TODO:

• Run this against the v1.1.0 version of Cluster API code to check if the test captures the unexpected rollout.

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 #

[ykakarap]

/hold

[sbueringer]

@ykakarap I think you could also temporarily add a revert-commit to this branch to test if the test would detect the issue

[ykakarap]

@ykakarap I think you could also temporarily add a revert-commit to this branch to test if the test would detect the issue

I have a branch with this commit 6ae0a73 dropped. Will be testing it against this test branch.

[ykakarap]

I have a branch with this commit 6ae0a73 dropped. Will be testing it against this test branch.

Tested it against this version of code (causes kcp rollout on clusterctl upgrade). The test captures the rollout and fail as expected. Dropping WIP.

[sbueringer]

/test pull-cluster-api-e2e-main

[sbueringer]

lgtm from my side

[fabriziopandini]

/lgtm

[sbueringer]

/lgtm
/approve

[fabriziopandini]

@ykakarap can we remove the hold?

[ykakarap]

/hold cancel

[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