break up infinite update loop #137

[bvoss]

#137

[gianrubio]

Nice job @bvoss, the nginx controller do the same treatment to compare ingress resources.

[munnerz]

Thanks very much for this @bvoss. In future we may look at some kind of hash based check of the ingress spec to determine whether to update, but in the meantime this works perfectly.

[ahmetb]

Is this released in a tagged version? I am using jetstack/kube-lego:0.1.4 but still seeing this behavior. Opened #216 and #198. (edit: looks like the latest release doesn't have the commit.)

[gianrubio]

Please try the canary image: jetstack/kube-lego:canary

On Wed, 28 Jun 2017 at 04:21, Ahmet Alp Balkan ***@***.***> wrote: Is this released in a tagged version? I am using jetstack/kube-lego:0.1.4 but still seeing this behavior. Opened #216 <#216> and #198 <#198>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#204 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFbljILhpFaEb6-zCAjl7sbSzysh_I4Aks5sIbiogaJpZM4N1dO1> .

-- Giancarlo Rubio

[naveensrinivasan]

@munnerz With the canary release, we are getting any acme challenge which is not getting the certs. Any clue as to what we could do?