-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Divide KCP upgrade e2e test into multiple tests #4672
Comments
cc @jan-est |
Thanks @sedefsavas |
/kind feature |
/help |
@fabriziopandini: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
I can work on this one! @fabriziopandini @jan-est |
I am going to go ahead and assign myself, If anyone is already working on it feel free to unassign me. /assign @tcordeu |
/lifecycle active |
KCP upgrade tests include 2 HA cluster upgrade tests which takes too long for providers.
For the providers that parallelize their e2e tests, calling a time-consuming cluster-api test spec reduces the parallelization benefits. Instead dividing these tests will allow providers to choose which test to call and parallelise accordingly.
I propose to place scale-in-rollout test to a separate spec.
The text was updated successfully, but these errors were encountered: