Same host in multiple namespaces leads to multiple certificate requests

[anurag]

I am using the same TLS host in multiple Ingress resources that are all in different namespaces (but backed by the same nginx Ingress controller). kube-lego requests a new certificate for each new Ingress/namespace combination, running up against Let's Encrypt rate limits.

Expected behavior: if a certificate has been requested for a host in an existing namespace, a new certificate should not be requested again if the same host is encountered in an Ingress in a different namespace.

[rtyler]

I uninteionally exceeded the Let's Encrypt rate limit on a domain whilst running into this issue (oops!).

I'm willing to bet other folks are unintentionally sending more requests to Let's Encrypt like I was, but are lucky enough to not have enough hosts/namespaces to notice. 🤷‍