Support for same host duplicated across ingress objects about kube-lego HOT 7 OPEN

Can someone merge #142 ?

from kube-lego.

I was just scared by the complexity of implementing this. It should not be that hard after all, as we are assessing the host information as aggregated information once a change happens. But not exactly a priority for me...

from kube-lego.

Does it also skip certificates renewal? I am having the same problem :(

from kube-lego.

Any update on this? Or any place I can help implement it?

from kube-lego.

I'm running with #142 in production, for the same use case (multiple ingress objects, each contributing parts of the whole).

from kube-lego.

Just ran into this today. GKE requires running two separate Ingresses for handling IPv4 and IPv6 traffic, so there are valid scenarios that this overzealous protection is breaking. Guess I'll try cert-manager or #142.

from kube-lego.

I've just hit this when the certificate expired. I've set the newer ingress to use a different secret and kube-lego seems to have sorted this out (they are the same host). Are there any risks doing this?

from kube-lego.