Closed arno01 closed 6 years ago
Hey @arno01 - thanks for this! I've not got any IPv6 test environments, so feedback like this is very valuable.
Was there a particular reason for changing the image version to alpine 3.6? I've not attachment to alpine 3.5, but it does increase the surface for things to go wrong as a result!
If you could remove just that one commit, I'll merge this in!
@munnerz I am glad to help making kube-lego better ;-)
There was no particular reason for bumping the alpine, I have checked, the 3.5 should be fine to use until 2018-11-01 (YYYY-MM-DD) as per https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases
@munnerz PTAL
FWIW this fixed kube-lego for our sites that have both IPv4 and IPv6 addresses.
quay.io/abh/kube-lego:20170922-ipv6
Without this PR the http-01 challenge (
/.well-known/acme-challenge
) fails in a setup where one has IPv6 (AAAA DNS record) set.IPv4 probe succeeds
IPv6 probe fails
Introduced by https://github.com/jetstack/kube-lego/pull/114 Potentially relates to https://github.com/jetstack/kube-lego/issues/66