-
Notifications
You must be signed in to change notification settings - Fork 1.4k
⚠️ Clusterctl v1alpha3 should not upgrade to v1alpha4 #4268
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 v1alpha3 should not upgrade to v1alpha4 #4268
Conversation
/hold cancel |
/test pull-cluster-api-test-release-0-3 |
e8c8768
to
abd5fd3
Compare
/test pull-cluster-api-test-release-0-3 |
/retest |
abd5fd3
to
4c066a8
Compare
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
[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 |
/retest |
4c066a8
to
1f4f722
Compare
/lgtm |
What this PR does / why we need it:
This is a backport of #4202
Cluster API v1alpha4 is introducing changes in how providers are deployed (see e.g webhooks running with manager).
As a consequence, clusterctl version v1alpha3 should not be allowed to upgrade to v1alpha3 clusters
Which issue(s) this PR fixes:
Rif #4192
/milestone v0.3.x
/hold
for #4202 to merge