8000 Fix mount persistentVolumeClaim by shizacat · Pull Request #30 · cryptpad/helm · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fix mount persistentVolumeClaim #30

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

shizacat
Copy link
@shizacat shizacat commented May 20, 2025

Error when usage persistent volume

https://kubernetes.io/docs/concepts/storage/volumes/

@@ -46,10 +46,6 @@ spec:
volumeMounts:
- name: cryptpad-data
mountPath: /cryptpad/data
{{- if and .Values.persistence .Values.persistence.cryptpad.data.existingClaim }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In theory, this block is only rendered if you set up a value for: persistence.cryptpad.data.existingClaim

I don't understand why to remove this option for fix. Maybe if this rendered part is with error (perhaps issue is only indent).

It should be nice to continue to support the option to someone use custom volume claim.

Perhaps you can explain the deployment scenario to better understand error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0