-
Notifications
You must be signed in to change notification settings - Fork 199
Revert to vm-op api version v1alpha4 for vks #3697
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
base: release-3.6
Are you sure you want to change the base?
Revert to vm-op api version v1alpha4 for vks #3697
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: nikhilbarge The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @nikhilbarge. Thanks for your PR. I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
53dabf5
to
417bfdc
Compare
FAILED --- Jenkins Build #496 |
FAILED --- Jenkins Build #498 |
/ok-to-test |
} | ||
|
||
// getVmsvcVM fetches the vm from the specified ns | ||
func getVmsvcVM5( |
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.
@nikhilbarge can't we just use getVmsvcVM4
func and remove this one?
@nikhilbarge could you update the description explaining why we're removing VM Snapshots? |
@nikhilbarge what are the compatible Supervisor versions for VKS 3.5? Just wondering if our code needs to handle vm versions from alpha1 to 4 |
vmoperatorv1alpha1 "github.com/vmware-tanzu/vm-operator/api/v1alpha1" | ||
vmoperatorv1alpha2 "github.com/vmware-tanzu/vm-operator/api/v1alpha2" | ||
vmoperatorv1alpha3 "github.com/vmware-tanzu/vm-operator/api/v1alpha3" | ||
vmoperatorv1alpha4 "github.com/vmware-tanzu/vm-operator/api/v1alpha4" |
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.
Can we name this import to vmoplatest
or something similar so that we don't have to change so many lines every time we move to a new version?
Let's follow the same wherever applicable.
What this PR does / why we need it:
Revert to vm-op api version v1alpha4 for VKS release.
VKS should use only GAed versions of VMOP api and not api version under development.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Testing done:
Manual Testing:
Tested with supervisor have VirtualMachines with VMOP api version v1alpha4
Full logs for manual-testing-with-supervisor-v1alpha4.log
csi-controller-logs-with-supervsior-v1alpha4.log
csi-syncer-with-supervsior-v1alpha4.log
csi-node-with-supervsior-v1alpha4.log
Tested with supervisor have VirtualMachines with VMOP api version v1alpha2
revert-v1alpha4-manual-test-with-supervisor-v1alpha2.log
revert-v1alpha4-csi-controller-with-supervisor-v1alpha2.log
revert-v1alpha4-csi-syncer-with-supervisor-v1alpha2.log
revert-v1alpha4-csi-node-with-supervisor-v1alpha2.log
Special notes for your reviewer:
Release note: