Galaxy with CVMFS seems to work on newer kubernetes

**** This isn't a bug, I just want to point out that CVMFS seems to work better now.... ***

Hi, I saw this pull request https://github.com/cernops/cvmfs-csi/pull/35 on the cernops/cvmfs-csi and decided to try it. I added a few edits in a `new_provisioner` branch https://github.com/cyrilcros/cvmfs-csi/blob/new_provisioner/deployments/helm/cvmfs-csi/values.yaml

That's been working well for me, notably because it has a different `csi-cvmfsplugin` image that solves some issues (https://github.com/cernops/cvmfs-csi/issues/26). I just added some quick other changes like in this pull request https://github.com/cernops/cvmfs-csi/pull/22/files , or removing the attach component as in https://github.com/cernops/cvmfs-csi/issues/29 .

I am getting 504 timeout errors from nginx I am now trying to fix, but now the PVCs are created as they should on Kubernetes 1.21...

Review deployments/helm/cvmfs-csi/values.yaml and the linked cernops/cvmfs-csi pull requests and issues first. Reproduce the Kubernetes 1.21 PVC behavior and the nginx 504 described here, then clarify which compatibility or configuration change is wanted; the current report does not define a patch or completion criteria.

Written by the indexing model from the issue text.