Ingress tls secrets only updated if delete+create is used (and not update)? about kube-lego HOT 4 CLOSED

Just tried that on a GKE cluster created today with kube-lego 0.1.3 and it worked without an issue.

Feel free to reopen if needed

from kube-lego.

As far as I understand it the problem lies in the GCE ingress controller. I could implement a work around for GCE ingresses, but I guess it would be way better to fix the behaviour in the ingress controller.

The clues I found are around this GCE ingress issue: kubernetes-retired/contrib#1396

Maybe we try to fix it there first...

from kube-lego.

I just tried this and it works as intended: kubernetes-retired/contrib#1396 (comment)

What version of Kubernetes are you running?

from kube-lego.

@bprashanth This being 21 days ago... probably Kubernetes 1.3.7 (guessing from the GKE release notes), or possibly a version or two behind, such as 1.3.5 or 1.3.6. Pretty sure it was NOT 1.2.x, as I remember upgrading to 1.3.4 or 1.3.5 from 1.2.x, and then moved on to 1.3.7

After I filed this issue, my clusters are now on 1.4.0 (which, now looking at the above release-notes, sure looks like I'm already a few micro versions behind :), and I haven't needed to replace certs yet, so I haven't seen the problem again.

If you think this issue should be fixed in 1.4.0, please mark this as "confirmation required" or some such, and I can confirm in about 2 months, when my next certs expire... :D

from kube-lego.