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

Adjust clusterctl upgrade jobs for v1.3 #6835

Closed
ykakarap opened this issue Jul 6, 2022 · 1 comment · Fixed by kubernetes/test-infra#26750 or kubernetes/test-infra#26779
Closed
Assignees
Labels
area/testing Issues or PRs related to testing kind/feature Categorizes issue or PR as related to a new feature.

Comments

@ykakarap
Copy link
Contributor

ykakarap commented Jul 6, 2022

Once we start development of CAPI v1.3 we have to adjust our clusterctl upgrade test jobs.
The goal is to have jobs which test clusterctl upgrade from the latest release of each currently supported contract version (v1alpha3 (v0.3.x), v1alpha4 (v0.4.x) and v1beta1 (v1.2.x).

We already have jobs for v0.3, v0.4 and v1.1. As we don't need the job for v1.1 anymore we can just change it for v1.2:
Job: periodic-cluster-api-e2e-upgrade-v1-1-to-main

  • Change name to "periodic-cluster-api-e2e-upgrade-v1-2-to-main"
  • INIT_WITH_BINARY should use v1.2.0
  • Change testgrid-tab-name to "capi-e2e-upgrade-v1-2-to-main"

/kind feature
/area testing

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/testing Issues or PRs related to testing labels Jul 6, 2022
@ykakarap
Copy link
Contributor Author

ykakarap commented Jul 6, 2022

/assign

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 kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
2 participants