Skip to content
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

Closed
sedefsavas opened this issue May 26, 2021 · 8 comments · Fixed by #4683
Closed

Divide KCP upgrade e2e test into multiple tests #4672

sedefsavas opened this issue May 26, 2021 · 8 comments · Fixed by #4683
Assignees
Labels
area/testing Issues or PRs related to testing help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.
Milestone

Comments

@sedefsavas
Copy link

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.

@sedefsavas
Copy link
Author

cc @jan-est

@jan-est
Copy link
Contributor

jan-est commented May 26, 2021

Thanks @sedefsavas
Is there anyone in the community who could like work on this one right away?

@fabriziopandini
Copy link
Member

/kind feature
/area testing
/milestone v0.4
(setting milestone 0.4 given it seems that the sooner the better)

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label May 26, 2021
@k8s-ci-robot k8s-ci-robot added this to the v0.4 milestone May 26, 2021
@k8s-ci-robot k8s-ci-robot added the area/testing Issues or PRs related to testing label May 26, 2021
@fabriziopandini
Copy link
Member

/help

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label May 26, 2021
@tcordeu
Copy link
Contributor

tcordeu commented May 26, 2021

I can work on this one! @fabriziopandini @jan-est

@tcordeu
Copy link
Contributor

tcordeu commented May 26, 2021

I am going to go ahead and assign myself, If anyone is already working on it feel free to unassign me.

/assign @tcordeu

@fabriziopandini
Copy link
Member

/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label May 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Issues or PRs related to testing help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants