self-hosted e2e tests should detect unexpected rollouts #6925
Labels
area/testing
Issues or PRs related to testing
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
User Story
The self hosted e2e tests currently do not detect if an operation results in rollout of KCP, MachineDeployments, etc.
We already test for the same in clusterctl upgrade e2e tests. This issue is to add a similar check to the self hosted tests as well.
Ref: #6094 (comment)
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
/area testing
The text was updated successfully, but these errors were encountered: