I’m running a Kubernetes cluster at 18.104.22.168 and was previously using kube-lego 0.1.3 to fetch certificates. A power outage caused my cluster to reboot, and post-reboot, it was resolving a particular domain name to the wrong IP address and proceeding to infinite-loop request a certificate for only one of the two domains in the ingress (a separate issue I’ve reported to the kube-lego github).
I’ve now fixed the resolving issue by installing dnsmasq on the host nodes, writing the /etc/hosts file accordingly, and putting that at a higher priority in the name server list. I’ve also updated to kube-lego 0.1.6 following the rate limiting discussion at https://github.com/jetstack/kube-lego/pull/329 so with any luck (knock on wood) even if I get some sort of DNS issue, my server should hopefully no longer hammer yours.
Would you please forgive me and unblock 22.214.171.124?