There is a problem with CVMFS CSI storage class naming when deploying two or more Galaxy instances to the same cluster. In particular the pvc-refdata.yaml template defines the storageClassName as {{ $.Release.Name }}-cvmfs. The release name is passed to the galaxy-cvmfs-csi-helm chart which is responsible for creating the storage class.
However, the cvmfs csi driver can only be installed once. If the driver is installed with the first deployment (call it galaxy1) then the storage class will be named galaxy1-cvmfs and the second deployment (call it galaxy2) won't be able to find it since it is looking for galaxy2-cvmfs.
If the csi driver is deployed independently the storage class will be named galaxy-cvmfs-csi-cvmfs and neither deployment will be able to find it. There is currently no way to change the name of the storage class created as the galaxy-cvmfs-csi-helm chart also hard codes the name as {{ $.Release.Name }}-cmfs
There is a problem with CVMFS CSI storage class naming when deploying two or more Galaxy instances to the same cluster. In particular the
pvc-refdata.yamltemplate defines thestorageClassNameas{{ $.Release.Name }}-cvmfs. The release name is passed to thegalaxy-cvmfs-csi-helmchart which is responsible for creating the storage class.However, the cvmfs csi driver can only be installed once. If the driver is installed with the first deployment (call it galaxy1) then the storage class will be named
galaxy1-cvmfsand the second deployment (call it galaxy2) won't be able to find it since it is looking forgalaxy2-cvmfs.If the csi driver is deployed independently the storage class will be named
galaxy-cvmfs-csi-cvmfsand neither deployment will be able to find it. There is currently no way to change the name of the storage class created as thegalaxy-cvmfs-csi-helmchart also hard codes the name as{{ $.Release.Name }}-cmfsFriends with https://github.com/CloudVE/galaxy-cvmfs-csi-helm/pull/19