Duplicate secret causes exhaustion of duplicate certificates for same name

[jetstack]

Duplicate secret causes exhaustion of duplicate certificates for same name

[jsindy]

Hit this issue as well, it would be best to have the ability to use wildcard or add subdomains to the same cert.

[scruplelesswizard]

Lets Encrypt doesn't currently offer wildcard certificates. This isn't a limitation in Kube-Lego.

Regarding adding multiple domains/subdomains in the same cert, this is possible. Just specify them in your ingress. There is documentation.

[GM12Tick]

Just happend to me, already had a certificate and this caused kube-lego to exhaust the rate limit, now i'm stuck 4 days without a way to recreate certificate :(

[FrederikNS]

We are running a dual setup with tazjin/kubernetes-letsencrypt and kube-lego, as we are migrating to using ingress resources instead of loadbalancer services. The TLS secrets created by tazjin/kubernetes-letsencrypt does not match the structure of kube-lego, so kube-lego tries to update the secrets and fails. Then it retries, and finally ends up in a rate limit.

This process is very error prone, as you have to be careful with deleting the old certificate, and ensuring that a new one won't be created before finally applying the kube-lego annotations.

[scruplelesswizard]

Stale, closing