Simplify Lets Encrypt Certificates Management for Kubernetes
1–10 of 18 posts
Re: Simplify Lets Encrypt Certificates Management for Kubernetes
#2It feels liberating to just get an SSL cert for any subdomain I need and have the whole process abstracted from me.
Re: Simplify Lets Encrypt Certificates Management for Kubernetes
#3I've been using this project on GKE for ~2 weeks now in combination with the nginx ingress controller. I have it configured to use the DNS challenge to get new certs so I don't have to expose an extra port as well. It feels liberating to just get an SSL cert for any subdomain I need and have the whole process abstracted from me.
Re: Simplify Lets Encrypt Certificates Management for Kubernetes
#4Re: Simplify Lets Encrypt Certificates Management for Kubernetes
#5I'm curious what advantages and tradeoffs it has over the project that it is based upon [1] for a person choosing between them. [1]: https://github.com/kelseyhightower/kube-cert-manager
* it does not support subdomains (only root domains)
* it only supports googlecloud as dns provider
* Bugs and PRs remain unanswered/unmerged
Meanwhile the linked project supports http, SNI and DNS challenges, with around 20 or so DNS providers available. It also supports managing certs for ingress objects directly.
Re: Simplify Lets Encrypt Certificates Management for Kubernetes
#6I'm curious what advantages and tradeoffs it has over the project that it is based upon [1] for a person choosing between them. [1]: https://github.com/kelseyhightower/kube-cert-manager
Largely, https://github.com/kelseyhightower/kube-cert-manager is incomplete * it does not support subdomains (only root domains) * it only supports googlecloud as dns provider * Bugs and PRs remain unanswered/unmerged Meanwhile the linked project supports http, SNI and DNS challenges, with around 20 or so DNS providers available. It also supports managing certs for ingress objects directly.
Re: Simplify Lets Encrypt Certificates Management for Kubernetes
#7Earlier quoted context omitted.
Largely, https://github.com/kelseyhightower/kube-cert-manager is incomplete * it does not support subdomains (only root domains) * it only supports googlecloud as dns provider * Bugs and PRs remain unanswered/unmerged Meanwhile the linked project supports http, SNI and DNS challenges, with around 20 or so DNS providers available. It also supports managing certs for ingress objects directly.
Does it support multiple SANs on a single cert? I want to streamline things like vanity domain redirections, where every domain I add requires me to refresh the cert.
Re: Simplify Lets Encrypt Certificates Management for Kubernetes
#8I'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)
Re: Simplify Lets Encrypt Certificates Management for Kubernetes
#9Doesn't seem quite as configurable but looks a bit simpler to implement.
Re: Simplify Lets Encrypt Certificates Management for Kubernetes
#10I'm curious what advantages and tradeoffs it has over the project that it is based upon [1] for a person choosing between them. [1]: https://github.com/kelseyhightower/kube-cert-manager