Ingress with MetalLb issues

I have the installed latest microk8s and enabled ‘nginx-ingress’ and ‘metallb’ addons

I have everything configured and works well, but I can’t seem to get to connect traffic between:

‘nginx-controller’ service

NAME                                TYPE           CLUSTER-IP       EXTERNAL-IP      PORT(S)                      AGE
x-ingress-ingress-nginx-controller   LoadBalancer   10.152.183.90    192.168.89.165   80:31080/TCP,443:31443/TCP

and the ingress it self

NAME              CLASS    HOSTS                 ADDRESS     PORTS     AGE
x-ingress         <none>   x.com + 83 more...   127.0.0.1   80, 443   2d8h

Also, the ingress appears to bind to address 127.0.0.1. From reading through the project, i understand that this is correct, although I previously (kubeadm, cloud providers) used to get a load balancer ip (ex 192.168.89.165 instead of 127.0.0.1 in this case)

Please note that the node is on a different ip 192.168.89.160 than the loadbalancer, as per MetalLb documentation

The ingress is working and serving traffic correctly when curl-ed on 127.0.0.1

Is this correct behaviour, is there a problem with the config, how to connect route traffic from the loadbalanced ingress service? I must be missing something, but can’t figure out what

Thank you very much!

[djjudas21]

No problem @Ramblurr glad it was useful.

@evilnick I also did a write-up of this on my blog. Feel free to steal anything that’s useful for the docs - consider it open source https://jonathangazeley.com/2020/12/30/load-balancing-ingress-with-metallb-on-microk8s/

[davidberglund]

Changed my mind about automatically creating the lb svc after looking at the bash scripts. Just that reference from Ingress docs to Metallb docs should be good enough and easier to maintain in the long run.