Unable to expose UDP port via NGINX Ingress Controller in k3s about ingress-nginx

[longwuyuan]

Check K3S dos for implementing a LB

[bbqf]

Thanks for the hint, I deployed the metallb and everything started to work like a charm. I'll see if this can be done with servicelb as well, but if anyone stumbles upon this - on a single host k3s running at home, you likely need Layer 2 LoadBalancer.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[longwuyuan]

/remove-kind bug

• The reason is that the traffic is not even ingested to the controller to begin with
• The service of type LoadBalancer created by the ingress-nginx installation is in pending state so regardless of what test you do, they are all invalid
• You can implement the controller as per docs (specifically the infra provider's LB or metallb) and allow that port on host OS TCP/IP stack (in case you are using packet filters on host OS)

[longwuyuan]

and also add the output of kubectl get all -o wide to the issue description

[bbqf]

• The reason is that the traffic is not even ingested to the controller to begin with
• The service of type LoadBalancer created by the ingress-nginx installation is in pending state so regardless of what test you do, they are all invalid
  This is what confuses me: I've seen the pending state as well, however http(s) traffic is ingested perfectly, including routes, etc.

• You can implement the controller as per docs (specifically the infra provider's LB or metallb) and allow that port on host OS TCP/IP stack (in case you are using packet filters on host OS)
  There's a servicelb that comes with the k3s installation (it's a single node installation on a pc running in my basement). However if it's enabled, it doesn't get created due to ports 80 and 443 being taken by ingress-nginx-controller.

I am sure I am missing some basic stuff, but that's exactly the problem - I cannot identify which one.

[longwuyuan]

https://kubernetes.github.io/ingress-nginx/deploy/#rancher-desktop