where to store acme.json when using traefik as ingress controller

I am using traefik as the ingress controller and need to setup a storage path that can be persisted across restarts of deployments. Where can the file acme.json be stored so all nodes can access the information? Is it possible to store in etcd as key/value pairs?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Unfortunately, Traefik2’s community edition doesn’t have any way besides local files to store certs. Pre Traefik2 did support key-value stores (etcd, consul, etc.), which I found very hard to set up and get right.

I’m slowly working on modifying Traefik to support a shared storage solution. I have the basics working, but there are a few complex scenarios that I need to account for (multiple nodes trying to renew the same cert, etc.).

More info can be found here: