-
Notifications
You must be signed in to change notification settings - Fork 33
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
Upgrade to CAPI v1.3 #248
Comments
/milestone v0.5 |
@chrisdoherty4 |
I was giving thought to users who want to upgrade CAPC but are using CAPI 1.3. Going through the motions of 1.3 then 1.4 would give them an upgrade path. Are you saying we shouldn't worry? |
I took a look at the changes between CAPI versions and what we're using in CAPC and I think upgrading straight to 1.4 is OK. |
@chrisdoherty4 I used CAPC v0.4.8 with various clusterctl versions (1.2,1.3,1.4) without any issue it may be not required to use the same capi version in capc. |
Summary
CAPC v0.4 uses CAPI v1.2. To provide users with at least 1 CAPC release using CAPI 1.3, I'm proposing we do a v0.5 release that uses CAPI 1.3 before upgrading to CAPI 1.4.
/kind feature
The text was updated successfully, but these errors were encountered: