Closed pichouk closed 7 years ago
To the first point, it is likely related to the recent Let's Encrypt outage (although your domain should be pointing to a web server before requesting a certificate).
In the short term, the workaround that resolved the 504s for me was deleting the kube-lego-account
secret and redeploying kube-lego
to the cluster.
Yes my configuration was not good on this example, I was just reporting because I think kube-lego should not crash when Let's Encrypt return an HTTP 504. This is not a big issue, since Kubernetes restart the pod instantly, but still annoying. Can we imagine a behavior where it only skip this request ?
Why close the issue when it's still a problem?
Even if this repo is dead, i think closing something that is not fixed is not good.
I just noticed that my kube-lego container crash a lot. I have this log line just when it crash :
It happens just after it try a certificate request for a domain which not (yet) point to my server. I don't know if :
In any case, I think it is a problem that the container crash if it run into an HTTP504.