✨ Promote CAPI v1beta2 conditions in CAPIBM v1beta3 api's#2623
✨ Promote CAPI v1beta2 conditions in CAPIBM v1beta3 api's#2623Karthik-K-N wants to merge 1 commit intokubernetes-sigs:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Karthik-K-N The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/hold |
|
Tested by creating a normal PowerVS cluster |
|
Suspecting a bug upstream and created a PR kubernetes-sigs/cluster-api#13336, Lets wait to hear back from the maintainer, This PR is blocked till then |
|
With Infra creation flow |
2e86ad0 to
5846f09
Compare
5846f09 to
96e2dc9
Compare
What this PR does / why we need it:
This PR promots conditions for IBMPowerVSCluster, IBMPowerVSMachine and IBMPowerVSImage resources, Following changes are done
Necessary conversion functions are added and udpated fuzz tests to make sure no data is lost during conversions.
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 # Part of #2401
Special notes for your reviewer:
In CAPI the apiversion is v1beta2 but for CAPIBM its v1beta3, so we are using some CAPI's helper functions to convert the status, there the function name looks like v1beta1 to v1beta2 and vice versa, We are not supposed to get confused with that.
/area provider/ibmcloud
Release note: