ingress-nginx not giving external ip / not creating a lb about hetzner-k3s HOT 9 CLOSED

@khustochka sorry for the late reply. here is what I did basically added the hetzner-specific metadata there in the Nginx ingress yaml file that is used to install the ngnix ingress, I downloaded from their github and edited before applying into my cluster and manually applied. the location and private ip

metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.10.0
  name: ingress-nginx-controller
  namespace: ingress-nginx
  annotations: 
    load-balancer.hetzner.cloud/location: nbg1
    load-balancer.hetzner.cloud/use-private-ip: "true"

from hetzner-k3s.

@0xMALVEE Thanks a lot for your answer!

In my case the cause of the issue turned out to be a bit different, I will describe it here in case someone has the same.

The annotation I was missing was:

 load-balancer.hetzner.cloud/http-redirect-https: 'false'

https is correct here, because if you google it, a lot of pages mention load-balancer.hetzner.cloud/http-redirect-http (without s). That was my problem.

from hetzner-k3s.

fixed it. by adding anotattions under metadata.

from hetzner-k3s.

@0xMALVEE Do you mind telling what exactly you did to fix this. In which file did you added "annotations under metadata"? Would appreciate greatly!

I am having the same issue. Although I went to hetzner admin and manually added the target to the load balancer, and services to the target. Weirdly, after this https connection somehow started to work, but http did not (returning status 400 Bad request). And no External IP appeared anyway.

from hetzner-k3s.