Open
Conversation
By default, when persistence is enabled, the volume "nextcloud-main" is
used to store Nextcloud data. The chart offers an option to create an
extra PVC using persistence.nextcloudData.
However, it is not possible to mount data from an external source. Even
though extraVolumes and extraVolumeMounts are available, the data folder
is either sourced from "nextcloud-main" or "nextcloud-data".
By providing an option to skip mounting the "data" subfolder when using
the main persistence option, but not the nextcloudData option, it is
possible to provide a custom volume mount based on a different volume
specified in extraVolumes.
This allows, for example, to supply an NFS mount point:
```yaml
nextcloud:
extraVolumes:
- name: data
nfs:
path: /mnt/nextcloud
server: my-nfs-server.example.com
extraVolumeMounts:
- name: data
mountPath: /var/www/html/data
persistence:
# Create a PVC to store Nextcloud application data
enabled: true
# But don't mount the user data folder, as it is provided above
dataVolumeMount: false
```
Signed-off-by: Florian Ruechel <code@inexplicity.de>
Collaborator
|
There is already a |
Author
@wrenix Unfortunately, this does not work unless I'm missing something: If Do you have a suggestion how I could achieve my objective with the existing options? I can't find a way to stop something from being mounted at the data path, either the separate volume or the main volume, but I want to provide my own. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of the change
By default, when persistence is enabled, the volume "nextcloud-main" is used to store Nextcloud data. The chart offers an option to create an extra PVC using
persistence.nextcloudData.However, it's not possible to mount data from an external source. Even though
extraVolumesandextraVolumeMountsare available, the data folder is either sourced from "nextcloud-main" or "nextcloud-data".By providing an option to skip mounting the "data" subfolder when using the main persistence option, but not the
nextcloudDataoption, it is possible to provide a custom volume mount based on a different volume specified inextraVolumes.This allows, for example, to supply an NFS mount point:
Benefits
Users with specific storage setup can customise how their data gets mounted. For example, I have an existing Nextcloud installation that I want to migrate to Kubernetes, but the data is already in an NFS server and I just want to mount that.
Possible drawbacks
It's possible I missed a configuration combination that doesn't make sense here, there are many ways to combine options in this chart.
Applicable issues
N/A
Additional information
I've first tried to use the NFS CSI driver, but it caused quite a few issues. This would have worked without needing to change the helm chart. However, it did not work out due to all problems this caused me.
Checklist
Chart.yamlaccording to semver.