-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Galaxy with CVMFS seems to work on newer kubernetes #342
Comments
Thank you for pointing out that PR!! |
This is super helpful, thanks @cyrilcros. It still looks like the repo is generally behind on maintenance, and the last merged PR was in May, 2020. Perhaps we need to maintain a fork ourselves at https://github.com/CloudVE/cvmfs-csi that will generally work for this helm chart. Another, longer term alternative that was contemplated was to sync all the CVMFS data over to S3 and to switch to S3FS as an alternative using something like: https://github.com/ctrox/csi-s3. |
Yes, from what I have seen the Helm chart needed just minor work, but the CSI plugin itself needs an update. The |
@cyrilcros I am trying to get all of these changes merged into our helm charts, but the
Is this still working for you? |
**** This isn't a bug, I just want to point out that CVMFS seems to work better now.... ***
Hi, I saw this pull request cvmfs-contrib/cvmfs-csi#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.yamlThat's been working well for me, notably because it has a different
csi-cvmfsplugin
image that solves some issues (cvmfs-contrib/cvmfs-csi#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 cvmfs-contrib/cvmfs-csi#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...
The text was updated successfully, but these errors were encountered: