clusterctl upgrade e2e tests should detect if upgrade causes unexpected rollouts

[ykakarap]

User Story

The clusterctl upgrade e2e tests currently do not detect if an upgrade operation results in rollout of KCP, MachineDeployments, etc.

Having such a test could help in detecting cases like #6093.

Detailed Description

[A clear and concise description of what you want to happen.]

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/kind feature

[ykakarap]

/assign

[ykakarap]

We might benefit for doing similar checks in the clusterctl move e2e tests too.

[sbueringer]

+1 I assume you mean extending the existing clusterctl upgrade test
+1 to doing the same for the self hosted test (which uses clusterctl move)

[vincepri]

/milestone v1.2
/priority important-soon
/area testing

[sbueringer]

This has been implemented for the clusterctl upgrade test: #6184
So I think only doing the same for the self-hosted test is left.

[ykakarap]

This has been implemented for the clusterctl upgrade test: #6184 So I think only doing the same for the self-hosted test is left.

Issue for adding rollout check to self hosted e2e tests: #6925

[sbueringer]

Okay. I'll close this issue given we have a separate one for self-hosted

/close

[k8s-ci-robot]

@sbueringer: Closing this issue.

In response to this:

Okay. I'll close this issue given we have a separate one for self-hosted

/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.