You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hello!
I don't know if this problem has been solved (I didn't find any requests among Issues), but I would really like to have support for adding disks not in one VApp, but in different ones (or to view all VMs at the Cloud Director level).
For example: I install a Kubernetes cluster, and for parallel installation of nodes in Cloud Director, I use the same name of node on the vApp name. And i have no ideas how i can configure vcloud-csi-config.yaml for work on daemonset which use only same vApp like node name
The possibility to specify the vAppName variable * in the vcloud-csi-config.yaml configuration file or not specify it at all, so that a search is performed among all VMs in the current vdc
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Hello!
I don't know if this problem has been solved (I didn't find any requests among Issues), but I would really like to have support for adding disks not in one VApp, but in different ones (or to view all VMs at the Cloud Director level).
For example: I install a Kubernetes cluster, and for parallel installation of nodes in Cloud Director, I use the same name of node on the vApp name. And i have no ideas how i can configure vcloud-csi-config.yaml for work on daemonset which use only same vApp like node name
vApp_name : VM_name
node01.k8s.domain.local : node01.k8s.domain.local
node02.k8s.domain.local : node02.k8s.domain.local
Describe the solution you'd like
The possibility to specify the vAppName variable * in the vcloud-csi-config.yaml configuration file or not specify it at all, so that a search is performed among all VMs in the current vdc
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: