Skip to content
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

Closed
ekjuanrejon opened this issue Nov 26, 2019 · 5 comments
Closed

Persistent volume claim #40

ekjuanrejon opened this issue Nov 26, 2019 · 5 comments
Labels
kind/enhancement New feature or request

Comments

@ekjuanrejon
Copy link

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

@dtomcej
Copy link
Contributor

dtomcej commented Nov 26, 2019

Doing this would limit your replicas to 1.

Not sure that is the correct thing to do.

@Mokto
Copy link

Mokto commented Nov 26, 2019

Or you use a PVC that works with ReadWriteMany.

Like EFS.

@ekjuanrejon
Copy link
Author

Okay. Am just concerned that while updating the arguments restarts the pod and might hit lets encrypt rate limit? How to avoid that?

@sennerholm
Copy link

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?

@ldez ldez changed the title Persisten volume claim Persistent volume claim Mar 12, 2020
@mmatur
Copy link
Member

mmatur commented Mar 12, 2020

Fixed by #86

@mmatur mmatur closed this as completed Mar 12, 2020
@mmatur mmatur added the kind/enhancement New feature or request label Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants