-
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
Add E2E test to verify workload cluster upgrades #4043
Comments
/assign |
Any reason we've picked these two specific Kubernetes versions? |
/milestone v0.4.0 |
+1, While I think it makes sense to have something as the defaults, I would like to see something that is more easily configured at runtime that would allow for automating prow jobs more easily. |
The idea was to start with a single job which tests one of the upgrade paths mentioned in the #3693 (comment). Once that gets done, we raise new issues for all the other upgrade tests required and ask some help from the community to finish those off.
That is the end goal, to keep the test/job configurable enough to introduce more upgrade paths easily. |
As a reminder, upgrade in this context should include upgrading the control plane and the workers (including machines controlled by MachineDeployments and machines controlled by MachinePools) |
#3916 merged, so now this activity is unblocked |
@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. |
Updating this story to include the entire test matrix for workload cluster upgrade testing. |
/retitle Add E2E test to verify workload cluster upgrades |
/lifecycle active |
Is this being worked on? |
yes |
User Story
As a developer, I would like to run an E2E test to verify upgrading CAPI workload cluster between 2 supported versions.
Detailed Description
Anything else you would like to add:
For the complete discussion on the introduction of these tests, look at #3693 (comment) .
TL;DR We need to add E2E tests to verify the upgrades between supported k8s versions.
/kind feature
The text was updated successfully, but these errors were encountered: