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
Persistent volume claim #40
Comments
Doing this would limit your replicas to 1. Not sure that is the correct thing to do. |
Or you use a PVC that works with ReadWriteMany. Like EFS. |
Okay. Am just concerned that while updating the arguments restarts the pod and might hit lets encrypt rate limit? How to avoid that? |
If you have an PVC you maybe should convert it to a statefulset so it's not depending on having a readwritemany storage? But is the certificates really fetched from lets encrypt? Aren't they stored in the secret created by cert-manager? |
Fixed by #86 |
Can the chart be updated to use PVC to store the certs. right now every time the pod restarts it has to get certs from lets encrypt
The text was updated successfully, but these errors were encountered: