Merge https://github.com/kubernetes/cloud-provider-vsphere:master (55e3183) into main

[cloud-team-rebase-bot]

Summary by CodeRabbit

• Chores

  • Go toolchain set to 1.26; broad dependency refresh across modules.
  • CI/build images and workflow checkout pins updated; security scanner bumped.
  • Helm chart metadata, values, and repo index updated; README compatibility matrix revised.

• New Features

  • Default controller image/tag advanced to v1.36.0 and manifests for v1.36 created.
  • Runtime option to select VM Operator API version; multi-version adapter factory added.
  • RBAC expanded for Endpointslices and dual-stack service support.

• Tests

  • Many new and updated unit tests covering adapters, clients, VMService, and dual-stack behaviors.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

Walkthrough

Introduce a version-agnostic VM Operator adapter/factory and hub types; refactor CPI components (instances, loadbalancer, zones, vmservice) to use the adapter; add adapters (v1alpha2, v1alpha5, v1alpha6) with fakes/tests; remove legacy vmoperator client code; plus CI, tooling, chart, manifest, and module/version bumps.

Changes

VM Operator adapter + CPI wiring (single DAG)

Layer / File(s)	Summary
Hub types & interface pkg/cloudprovider/vsphereparavirtual/vmoperator/types/types.go, pkg/cloudprovider/vsphereparavirtual/vmoperator/interface.go	Add version-agnostic hub types and replace the versioned vm-operator interface with VirtualMachines() / VirtualMachineServices() accessors operating on hub types.
Factory pkg/cloudprovider/vsphereparavirtual/vmoperator/factory/factory.go, .../factory_test.go	Add NewAdapter(version, cfg) dispatcher selecting v1alpha2/v1alpha5/v1alpha6 adapters; tests for supported/unsupported versions.
Adapters (impl, conversion, dual-stack, fakes, tests) pkg/cloudprovider/vsphereparavirtual/vmoperator/adapter/v1alpha2/*, .../v1alpha5/*, .../v1alpha6/* (including fake/* and *_test.go)	Introduce adapters implementing vmop.Interface, conversion helpers between API types and hub types, dual-stack handling in v1alpha6, plus per-version fake helpers and comprehensive adapter tests.
Provider dynamic clients pkg/cloudprovider/vsphereparavirtual/vmoperator/provider/v1alpha2/client.go, .../v1alpha5/client.go, .../v1alpha6/client.go + tests	Add dynamic-client-based provider clients (GVRs, constructors, CRUD/list methods) consumed by adapters and covered by tests.
Remove legacy client scaffolding pkg/cloudprovider/vsphereparavirtual/vmoperator/client/*, .../client/*_test.go, .../fake_client.go (deleted)	Delete previous versioned client and fake scaffolding replaced by the adapter/provider stack.
VMService layer -> hub types pkg/cloudprovider/vsphereparavirtual/vmservice/vmservice.go, pkg/cloudprovider/vsphereparavirtual/vmservice/types.go, .../vmservice_test.go	Refactor VMService to use VirtualMachineServiceInfo hub types; rewrite create/update/get/delete flows, add comparison/normalization logic and IPFamily/dual-stack handling; update tests.
CPI components wiring pkg/cloudprovider/vsphereparavirtual/cloud.go, loadbalancer.go, instances.go, zone.go and tests	Add --vm-operator-api-version flag; Initialize uses factory.NewAdapter; NewLoadBalancer, NewInstances, NewZones accept vmop.Interface; discovery and instance logic updated to hub types; tests switched to adapter fakes.
Load balancer status mapping & tests pkg/cloudprovider/vsphereparavirtual/loadbalancer.go, loadbalancer_test.go	Rewrite to use VMServiceInfo status for LoadBalancerStatus (map IP/Hostname entries), update Ensure/Update/Get to use vmservice adapter; add unit test for ingress conversion.

sequenceDiagram
    participant CPI as CloudProvider (Initialize)
    participant Factory as vmoperator.Factory
    participant Adapter as vmoperator.Adapter (v1alpha*)
    participant Dyn as dynamic API server
    participant VMService as VMService / LoadBalancer

    CPI->>Factory: NewAdapter(apiVersion, rest.Config)
    Factory->>Adapter: construct adapter instance
    Adapter->>Dyn: CRUD / Get / List VirtualMachine(s) and VirtualMachineService(s)
    Dyn-->>Adapter: unstructured typed objects
    Adapter-->>CPI: hub types (VirtualMachineInfo / VirtualMachineServiceInfo)
    CPI->>VMService: NewLoadBalancer/NewInstances/NewZones(vmop.Interface)
    VMService->>Adapter: Get/Create/Update VMService using hub types
    Adapter->>Dyn: Update/Create unstructured VMService (including dual-stack)
    Dyn-->>Adapter: updated object / errors
    Adapter-->>VMService: result (hub types) / errors

Loading

CI, tooling, and build updates (independent DAG)

Layer / File(s)	Summary
GitHub workflows (general) .github/workflows/auto-sync-gh-pages.yml, .github/workflows/bump-k8s-dep.yml, .github/workflows/bump-test-k8s-dep.yml, .github/workflows/generate-release-notes.yml	Bump actions/checkout usage from v6.0.1 → v6.0.2.
GitHub workflow (security) .github/workflows/weekly-security-scan.yaml	Repin actions/checkout to v6.0.2 and update actions/setup-go to v6.4.0.
Makefile / Trivy / Go default Makefile	Add GO_VERSION ?= 1.26.0; bump TRIVY_VER 0.49.1 → 0.69.2.
Cloud Build images cloudbuild.yaml, cloudbuild-nightly.yaml	Replace digest-pinned gcb-docker-gcloud image with named tag v20260205-38cfa9523f.
Go toolchain & modules go.mod, hack/tools/go.mod, test/e2e/go.mod	Bump Go versions to 1.26.0 (where present) and refresh many direct/indirect dependencies (k8s libs → v0.36.0, govmomi, OpenTelemetry, ginkgo/gomega, golang.org/x/*, etc.).

Helm, charts, manifests, and release artifacts (independent DAG)

Layer / File(s)	Summary
Helm chart metadata & values charts/vsphere-cpi/Chart.yaml, charts/vsphere-cpi/values.yaml, charts/vsphere-cpi/README.md	Bump chart appVersion and version to 1.36.0; default daemonset image tag → v1.36.0; adjust packaging VERSION snippet.
Chart templates RBAC charts/vsphere-cpi/templates/role.yaml	Add RBAC rule allowing get,list,watch on discovery.k8s.io/endpointslices.
Helm index & packaged chart index.yaml	Replace vsphere-cpi entry 1.35.1 with 1.36.0 and update timestamps/digest/urls.
Manifests & release manifests manifests/controller-manager/*, releases/v1.35/*, releases/v1.36/*, docs/book/tutorials/disable-node-deletion.yaml, releases/README.md, README.md	Update CPI image tags and add releases/v1.36 manifest; adjust docs and compatibility matrix entries.

Tests & supporting changes (scattered, same DAG as adapters)

Layer / File(s)	Summary
Unit/integration tests migrated to adapter fakes pkg/cloudprovider/vsphereparavirtual/*_test.go, vmoperator/adapter/*/fake/*	Migrate tests from legacy fake client to new adapter fake helpers; add adapter/client tests covering CRUD, conflict propagation, dual-stack scenarios, and resource-version pass-through.
Removed legacy tests/helpers pkg/cloudprovider/vsphereparavirtual/vmoperator/client/*_test.go, .../client/* (deleted)	Remove older dynamic client wrappers and their test suites replaced by new provider/adapters and test coverage.

Estimated code review effort

🎯 5 (Critical) | ⏱️ ~120 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

[openshift-ci]

Hi @cloud-team-rebase-bot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.