Closed yousafsyed-bg closed 4 years ago
Hi, might be both, but the message lookup api.hetzner.cloud on 10.43.0.10:53: server misbehaving
hints in the direction, that it's not a bug in the code but the DNS resolution on the fip-controller pod does not work.
Are the nginx-ingress and the fip-controller pods set up in a comparable manner (using the same network rules etc)? Could you validate (e.g. by running a pod with the fip-controller image and command /bin/bash) if the DNS resolution works fine in general?
Thanks for replying fast, I will try that and report back
Hey @yousafsyed-bg do you have some further info on this? :)
Since this is stale for about a month now I'll close the issue. Please feel free to re-open in case the problem persists.
I am trying to deploy the latest FIP controller but it keeps giving me following error
I have tested that networking from other deployments, for example from Nginx-ingress pods I can do curl requests to the hetzner-cloud API with the same API-token and it works but for some reason, the FIP controller is failing on API requests.
Is this a bug ? or I have misconfigured something
Update:
Redeployed the cluster it worked