TLS parameters from more dynamic providers and a default path for a no-config setup

<!-- DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. The issue tracker is for reporting bugs and feature requests only. For end-user related support questions, please refer to one of the following: - the Traefik community forum: https://community.containo.us/ --> ### Do you want to request a *feature* or report a *bug*? Feature ### What did you expect to see? Right now I use a Docker Compose file and configure everything as static configuration on the Traefik service command line, or dynamic configuration as labels on my various services. I have a requirement to use a specific custom wildcard TLS certificate for all services. This setup is possible today in Traefik v2.0, but I must provide a file to the Traefik service with the `tls.certificates` and `tls.options` parameters. Currently the TLS parameters cannot be set using labels. To eliminate the additional configuration file, the TLS parameters should be possible to set from container labels, and to designate a default path for default certificates that is automatically picked up by Traefik. The current documentation does not mention if a default path already exists, all examples use dummy `/path/to` paths. <!-- HOW TO WRITE A GOOD ISSUE? - Respect the issue template as much as possible. - The title should be short and descriptive. - Explain the conditions which led you to report this issue: the context. - The context should lead to something, an idea or a problem that you’re facing. - Remain clear and con

Posted by stellirin on Sep 26, 2019, 3:10 PM

Tags

• support (Other)

Related issues

• some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
• I think of this as the kiosk economy.
• What a goofy comment.
• There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
• Compose support in WSLc
• [RFC] Roadmap to v2.0