* 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.
Comments
I'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.
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.
Unfortunately, not currently, no :< It's trivial to get seperate certs, but getting them all on a single cert is not in yet.
I haven't used this yet but will say that lego (which this uses) is a joy to use.