11–18 of 18 posts
I thought I wanted this for a long time, but `kube-lego` gets me very similar results... without needing to inject credentials for my DNS provider to my cluster. I'm curious if others have thoughts on this vs kube-lego. (I would agree that I like the approach of this project quite a bit more than kelseyhightower's. This feels more complete, works with far more providers, etc)
I thought I wanted this for a long time, but `kube-lego` gets me very similar results... without needing to inject credentials for my DNS provider to my cluster. I'm curious if others have thoughts on this vs kube-lego. (I would agree that I like the approach of this project quite a bit more than kelseyhightower's. This feels more complete, works with far more providers, etc)
You can use http challenges with kcm as well. Which is what ensures you don't need to inject dns credentials.
edit: Oh my, and I can use this for the HTTP challenge and still use it with other Ingress controllers. I'd love to buy you a beer/rootbeer or something, I'm so tickled to have this!
Found this similar project a couple days ago: https://github.com/tazjin/kubernetes-letsencrypt Doesn't seem quite as configurable but looks a bit simpler to implement.
Earlier quoted context omitted.
You can use http challenges with kcm as well. Which is what ensures you don't need to inject dns credentials.
Whoa! This is really great! Thank you for this (and to think I was excited to see the Caddy secret backend, this is way better IMO)! edit: Oh my, and I can use this for the HTTP challenge and still use it with other Ingress controllers. I'd love to buy you a beer/rootbeer or something, I'm so tickled to have this!
What are the major difference between this and say kube-lego that might entice someone to switch?