-
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
🌱 clusterctl v1alpha4 should not install v1alpha3 providers #4200
🌱 clusterctl v1alpha4 should not install v1alpha3 providers #4200
Conversation
c62b77b
to
a281f28
Compare
/retest |
2 similar comments
/retest |
/retest |
/milestone v0.4.0 |
/retest |
1 similar comment
/retest |
/retitle 🌱 clusterctl v1alpha4 should not install v1alpha3 providers |
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.
/approve
/lgtm
/lgtm cancel @fabriziopandini squash commits please |
3629aea
to
3e572ed
Compare
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri 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 |
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.
/lgtm
/test pull-cluster-api-test-main |
1 similar comment
/test pull-cluster-api-test-main |
What this PR does / why we need it:
Cluster API v1alpha4 is introducing changes in how providers are deployed (see e.g webhooks running with manager).
As a consequence, clusterctl version v1alpha4 should not be allowed to install v1alpha3 providers
NB: While doing the change, also clusterctl version v1alpha4 should not be allowed to install v1alpha5 providers was implemented, and tests are now refactored in order to make changes for supporting the next contract less invasive.
This will also ensure easier backport
Which issue(s) this PR fixes:
Rif #4191