Report this

What is the reason for this report?

How to solve clusterissuer challenge timeouts?

Posted on December 11, 2019
thc

By thc

Setup: DO K8S Cluster w/ 2 nodes and 1 Ingress-NGINX LoadBalancer

I was wondering why certificate requests fail and found in the logs of the Challenge, that the self check GET request runs into timeout.

After looking closer the issue seems that when I try to make curl requests to my LoadBalancer public IP from inside of running pods, only the pods running on the node that the LoadBalancer currently points not to can make successful requests. All other requests from pods running on the other node are getting timeout.

Any advice on how to solve this? Thanks!



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
0

Accepted Answer

Posted the same issue on SO, and already got an answer there:

https://stackoverflow.com/questions/59286126/kubernetes-cluterissuer-challenge-timeouts

For me, this is an acceptable workaround for now. Hope this can help you.

same problem here, I can access the acme file from other machines, but not from a pod running on a node behind the load balancer.

I have another cluster setup a while ago and from there the challenge worked without issues.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.