Support / documentation for installation on clusters not managed via VCD-CSE

[butler54]

Is your feature request related to a problem? Please describe.

Currently our VCD installations have a small number of Kubernetes clusters of different flavours (e.g. OpenShift; micro Kubernetes) which have been installed manually. As a admin of those clusters I'd like to be able to use the CSI driver as opposed to relying on hostpath or NFS based storage.

Describe the solution you'd like

Instructions on using the CSI driver outside of the CSE. Im assuming this may require some modifications to the driver as well (e.g. cluster ID is no longer usable).

Describe alternatives you've considered

Some of the clusters have been provisioned due to vendor software constraints. This makes moving to TKG harder (but not impossible). The preferred solution would be to manage workloads via TKG & CSE deployed clusters.

Additional context

No response

[arunmk]

@butler54 can you try with a cluster_id of the form NO_RDE_<uuid>

[butler54]

Will do

[mate201]

I'm one the same boat here. I tried the cluster_id="NO_RDE_<uuid>" setting, and everything seems to work from my short testing.

[Vivida1]

Is it correct that you can randomly choose a uuid for the cluster_id="NO_RDE_<uuid>" setting?

[arunmk]

Is it correct that you can randomly choose a uuid for the cluster_id="NO_RDE_<uuid>" setting?

For the NO_RDE mode, since there is no central dedup, we just choose a random uuid.

[des1redState]

+1 - A couple of our self-managed Rancher clusters happen to be hosted on VCD, and we really need some basic documentation on installing/using this CSI. It doesn't have to be anything fancy, it just has to be adequate.

[des1redState]

@butler54 - if you happened to get this working, I'd really appreciate your guidance in the meantime.

[rolfbartels]

+1 It would be really helpful if there where some form of documentation.

[taocnrut]

Also not to forget that VM must have disk.EnableUUID = TRUE in order to attach named disk