-
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
🌱 e2e: add init versions for providers #7628
🌱 e2e: add init versions for providers #7628
Conversation
Skipping CI for Draft Pull Request. |
/test pull-cluster-api-e2e-full-main |
4cba044
to
2dd9751
Compare
/test pull-cluster-api-e2e-full-main |
2dd9751
to
2461425
Compare
/retest (GitHub rate limit when retrieving cert-manager YAML) /test pull-cluster-api-e2e-full-main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you
Just some nits, otherwise fine for me
test/e2e/clusterctl_upgrade.go
Outdated
// InitWithCoreProvider can be used to override the INIT_WITH_CORE_PROVIDER e2e config variable with a specific core provider | ||
// version to use when initializing the secondary management cluster, e.g. `cluster-api:v1.3.0` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// InitWithCoreProvider can be used to override the INIT_WITH_CORE_PROVIDER e2e config variable with a specific core provider | |
// version to use when initializing the secondary management cluster, e.g. `cluster-api:v1.3.0` | |
// InitWithCoreProvider specifies the core provider version to use when initializing the secondary management cluster, e.g. `cluster-api:v1.3.0`. | |
// If not set, the core provider version is calculated based on the contract. |
nit. same below (there is no INIT_WITH_CORE_PROVIDER)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Q: should we document these take precedence on InitWithProvidersContract? (same for the others)
2461425
to
f870c4e
Compare
Thank you for the reviews! I think I have addressed all comments now, PTAL 🙂 |
/test pull-cluster-api-e2e-full-main |
1 similar comment
/test pull-cluster-api-e2e-full-main |
/lgtm |
/retest |
@lentzi90 thanks for helping us in making test framework more flexible! |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherry-pick release-1.3 (but sorry won't make it into v1.3.0) |
@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.3 in a new PR and assign it to you. 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. |
@sbueringer: new pull request created: #7673 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. |
What this PR does / why we need it:
Support specifying the initial versions for providers in the e2e clusterctl upgrade test.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #7603