Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Failed to verify ACME account #641
Is this a BUG REPORT or FEATURE REQUEST?:
I deployed cert-manager with helm like this:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
the content of letsencrypt-prod.yaml is:
Anything else we need to know?:
I got around it by using kubeadm, although it was quite rough too!
@tcassaert by the way if you like to use kubeadm you can have my winning starting command:
(configured kubectl as in the kubadm example)
and tainted my single master as node too:
It seems like you have some strange DNS configuration going on, as the Let's Encrypt API URLs seem to be resolving to an address that points to your ingress controller. I'm not too sure exactly what's happened here, but it does not seem like an issue with cert-manager itself to me.
I'm going to close this to keep the issue board clear, and would advise you jump onto the #cert-manager channel in the Kubernetes slack so we can dig into your issues!