mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-01-15 22:38:07 +00:00
cdc411edf0
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Fix locating resourcepool-path specified in the vsphere.conf file **What this PR does / why we need it**: When volume is provisioned using the vsphere storage policy, `resourcepool-path` specified in the `vsphere.conf` file is used for creating a shadow/dummy VM. Dummy VM is temporarily created and then deleted once volume is created on the compatible Datastore. At present If user specifies `resourcepool-path` in the `vsphere.conf` file, volume provisioner is not able to locate the compute resource for the given path. This is because look up is made using `finder.DefaultComputeResource(ctx)` and `finder.ComputeResource(ctx, computePath)`, which is not correct. If user specifies name of the cluster or cluster path then provisioning works. This is resolved with using correct govmomi method - `func (f *Finder) ResourcePoolOrDefault(ctx context.Context, path string) (*object.ResourcePool, error)` **Which issue(s) this PR fixes** Fixes # https://github.com/vmware/kubernetes/issues/493 **Special notes for your reviewer**: Following testing is performed for this change. 1) specified resource-pool path in the `vsphere.conf` file and verified VM is created under the specified resource pool. ``` resourcepool-path="ClusterFolder-1/cluster-vsan-1/Resources/ShadowVMPool" ``` 2) If resource pool is not available, specified cluster's default resource pool path in the `vsphere.conf` file and verified volume provisioning works. For this case, VM is directly created under cluster. ``` resourcepool-path="ClusterFolder-1/cluster-vsan-1/Resources" ``` 3) Verified above with having multiple clusters with the same name in one datacenter. 4) Verified with empty resource pool path in the vsphere.conf file. ``` resourcepool-path="" ``` As expected, provisioning is failing with `Failed to provision volume with StorageClass "vsan-gold-policy": no default resource pool found`. Refer to this datacenter inventory for the path specified in the `resourcepool-path` configuration.  Current documentation describes `resourcepool-path`configuration is optional, which needs to be corrected once PR is merged. For policy based provisioning this is not an optional parameter. Documentation link: https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/existing.html **Release note**: ```release-note Fix for resourcepool-path configuration in the vsphere.conf file. ``` cc: @kubernetes/vmware
