fix: propagation of cvmfs alien and local cache #150
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CVMFS_CACHE_BASE
andCVMFS_ALIEN_CACHE
were previously advertised as being configurable via helm values.yaml, however were hardcoded volumeMounts and hardcoded defaults in the application code.I have adjusted the config loading of the automount binary to use the values in
/etc/cvmfs/default.local
if they are present and otherwise fall back on the previous hardcoded values ininternal/cvmfs/automount/automount.go
.Also added a basic set of go ci (borrowed from here).
Fixes: https://gitlab.cern.ch/kubernetes/storage/cvmfs-csi/-/issues/60