(wip) Update vm-operator spec to v1alpha2

kubernetes-sigs / vsphere-csi-driver

vSphere storage Container Storage Interface (CSI) plugin

https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/index.html

Apache License 2.0

293 stars 177 forks source link

(wip) Update vm-operator spec to v1alpha2 #2831

Open adikul30 opened 5 months ago

adikul30 commented 5 months ago

What this PR does / why we need it: vm-operator has shifted from API version v1alpha1 to v1alpha2. CSI moving it's client from v1a1 to v1a2 would mean the vm-op conversion webhook won't be involved thus saving time and resources.

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: https://github.com/kubernetes-sigs/vsphere-csi-driver/pull/2831#issuecomment-2048087621

Special notes for your reviewer:

Release note:

k8s-ci-robot commented 5 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adikul30

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: - ~~[OWNERS](https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/OWNERS)~~ [adikul30] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

divyenpatel commented 5 months ago

/ok-to-test

adikul30 commented 4 months ago

Build #1375 (Apr 9, 2024, 4:13:53 PM)
adkulkarni
PR 2831
Ran 13 of 816 Specs in 2659.499 seconds SUCCESS! -- 13 Passed | 0 Failed | 0 Pending | 803 Skipped PASS Ginkgo ran 1 suite in 46m6.024409434s Test Suite Passed make: Leaving directory `/home/worker/workspace/csi-wcp-precheckin/Results/1375/vsphere-csi-driver'

adikul30 commented 4 months ago

cc: @nikhilbarge

k8s-ci-robot commented 3 months ago

PR needs rebase.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

k8s-triage-robot commented 2 weeks ago

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle stale
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale