-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
k8s provider w/ acme? #752
Comments
In the 1.1 version (v1.1.0-rc2 released 2 days ago), you can enable |
@krancour I tested it with Kubernetes recently and wrote a post here : https://archifleks.github.io/blog/kubernetes-ingress/ basically if you are using a configmap like that It should work seamlessly :
|
@emilevauge @ArchiFleKs this looks like exactly what I am looking for. I'll take that for a test drive. Thanks! |
This worked like a charm. Thank you guys! |
@ArchiFleKs I followed your tutorial, but unfortunately my ingress controller always fails with a |
Hi @craigwillis85 could share the logoutput from the crashed traefik? |
@errm is there an easy way to do that? |
@errm I have an issue. I'm running |
@craigwillis85 can you log into the node and get the log from the docker daemon ? Did you use a host volume for acme storage ? One of the crash cause I've seen was du to a configuration error with acme storage |
I managed to get this working with the lets encrypt staging. So, all is good! On 23 Nov 2016 20:04, "Kevin Lefevre" [email protected] wrote:
|
Is there a comprehensive example of using the Kubernetes provider with ACME support?
It's really awesome that Traefik can be used as an ingress controller, but so far, what I can't get it to do is use ACME to request certificates for whatever hosts are named in my ingress resources. i.e. I still need to explicitly include the following in my toml:
Updating that configuration each time I add or modify ingresses doesn't seem ideal.
Can the ACME module work seamlessly with the k8s provider? Or is that not yet possible?
The text was updated successfully, but these errors were encountered: