You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey!
First of all, thanks for this amazing piece of software. It helps me a lot setting up a k3s-Cluster easily!
I have the following problem and am not sure if it's a potential bug, so I'd like to ask here.
If I set load-balancer.hetzner.cloud/hostname, e.g. to "app.mydomain.com", terraform stucks with Waiting for load-balancer to get an IP.... If I remove the hostname label, it works again
kubectl get svc -n nginx shows nginx-ingress-nginx-controller LoadBalancer 10.43.82.234 app.mydomain.com 80:32750/TCP,443:30272/TCP (so the IP is missing, instead it has the hostname)
I've noticed that my pods hat problems connecting to other pods using ipv4. This happened first when using cert-manager which was not able to resolve my domain (Accessing exposed service from inside #409) - so that's why I'm setting the hostname
I must say that I rolled out the change by editing the service directy, I didn't investigate a way to change this via terraform yet
Maybe you have an idea why this is happening? I unfortunately couldn't find the code for this yet to check if this is intended. However, this blocks me from updating my cluster unless I remove the hostname temprarily, do the upgrade and add it again.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey!
First of all, thanks for this amazing piece of software. It helps me a lot setting up a k3s-Cluster easily!
I have the following problem and am not sure if it's a potential bug, so I'd like to ask here.
load-balancer.hetzner.cloud/hostname
, e.g. to "app.mydomain.com", terraform stucks withWaiting for load-balancer to get an IP...
. If I remove the hostname label, it works againkubectl get svc -n nginx
showsnginx-ingress-nginx-controller LoadBalancer 10.43.82.234 app.mydomain.com 80:32750/TCP,443:30272/TCP
(so the IP is missing, instead it has the hostname)Maybe you have an idea why this is happening? I unfortunately couldn't find the code for this yet to check if this is intended. However, this blocks me from updating my cluster unless I remove the hostname temprarily, do the upgrade and add it again.
Thanks a lot
Beta Was this translation helpful? Give feedback.
All reactions