search

jetstack / kube-lego

DEPRECATED: Automatically request certificates for Kubernetes Ingress resources from Let's Encrypt
Apache License 2.0
2.16k stars 267 forks source link

renewal expiry date is incorrect #315

Closed one000mph closed 6 years ago

one000mph commented 6 years ago

I am using kube-lego with an nginx controller. I received several notifications that my cert would expire via the Let's Encrypt Expiry Bot. I thought that this was strange because kube-lego should renew the cert at 30 days. According to logs, lube-lego still thinks that my cert has 72.0 days of validity, but this does not seem to be correct. Can someone please help resolve this issue?

screen shot 2018-01-30 at 5 16 32 pm

Logs from kube-lego

context="ingress_tls" expire_time=2018-04-12 17:57:34 +0000 UTC name=community-api-ing namespace=default
time="2018-01-30T01:09:12Z" level=info msg="no cert request needed" context="ingress_tls" name=community-api-ing namespace=default
time="2018-01-30T09:09:12Z" level=info msg="cert expires in 72.4 days, no renewal needed" context="ingress_tls" expire_time=2018-04-12 17:57:34 +0000 UTC name=community-api-ing namespace=default
time="2018-01-30T09:09:12Z" level=info msg="no cert request needed" context="ingress_tls" name=community-api-ing namespace=default
time="2018-01-30T17:09:12Z" level=info msg="cert expires in 72.0 days, no renewal needed" context="ingress_tls" expire_time=2018-04-12 17:57:34 +0000 UTC name=community-api-ing namespace=default
time="2018-01-30T17:09:12Z" level=info msg="no cert request needed" context="ingress_tls" name=community-api-ing namespace=default
one000mph commented 6 years ago

This was caused by a problem with the gce ingress controller, not with kube-lego. sorry for the false alarm.