Is it possible to use a CIFS share as the persistence.nextcloudData.existingClaim ?
Open
Nobody has claimed this yet.
help wanted
needs info
Persistence
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
I saw in the log an error about setting the directory to 0700 ... for security, but I'd like to use the cifs share ... way to disable that check so it'll work anyway? This seems to prevent the use of cifs...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the Helm chart's persistence.nextcloudData.existingClaim handling and the 0700 directory-permission check described in the report. Determine whether a configurable exception can safely support a CIFS share, then verify the behavior for an existing claim and document the security trade-off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100