dns-udp can't find the listener

[CaiNiaoHui]

Describe the bug

Use the yaml file under examples-of-custome-resources/basic-tcp-udp folder to deploy.
The status of transport-server's dns-udp shows "Listener dns-udp donesn't exist"

To Reproduce
Steps to reproduce the behavior:

1. use the dns yaml to create cm, deployment, service
   
   
2. use the global-configuration.yaml to create nginx-configuration, and the global-configuration and pod I created are in the same namespace
   
3. use the transport-server-udp.yaml to create dns-udp. But the transportServer's status shows refused to listen.
   
   
   

Expected behavior
I hope TransportServer can successfully match with global configuration.

Your environment

• Version of the Ingress Controller - current version: v1.11.3
• Version of Kubernetes: v1.18.20
• Kubernetes platform: rancher v2.5.7
• Using NGINX Plus

[github-actions[bot]]

Hi @CaiNiaoHui thanks for reporting!

Be sure to check out the docs while you wait for a human to take a look at this 🙂

Cheers!

[jasonwilliams14]

@CaiNiaoHui
Can you check your deployment and verify you have specified your global configuration as part of the command line arguments?
https://docs.nginx.com/nginx-ingress-controller/configuration/global-configuration/command-line-arguments/

Specifically, you want to look for the following line:

- -global-configuration=$(POD_NAMESPACE)/nginx-configuration

If that is not set, add that setting then redeploy the ingress as well as your transportserver resources (per our example)
Let us know how that goes.

[CaiNiaoHui]

@jasonwilliams14
Thank you for your answer.
I find the question is my ingress controller DaemonSet don't add the configuration of "gloabl-configuration".
Then I add this setting, the transportServer can successfully match with global configuration.

[robincher]

Is there anyway i can set it via the helm values?

If there are services/pods residing outside of the typical namespace like nginx-ingress, how i can enable this in an automated way?

[pleshakov]

Hi @robincher

It is possible to configure the GlobalConfiguration resource via controller.globalConfiguration.spec See also https://github.com/nginxinc/kubernetes-ingress/blob/v1.12.1/deployments/helm-chart/values.yaml#L162-L169 In that case, it is also necessary to set controller.globalConfiguration.create to true

[sheetalshet]

Hello,

I am trying to expose the MQTT port using the TCP protocol, but it's not working. The same setup works on Rancher Desktop but fails on AKS.

Setup Details:

• Kubernetes Version: AKS k8s 1.30.2
• NGINX Ingress Controller Version: 3.6.2
• MQTT Service Port: 1883

Ingress-NGINX Controller Custom values.yaml:

controller:
  enableCustomResources: true
  service:
    type: LoadBalancer
    customPorts:
    - name: mqtt
      port: 1883
      protocol: TCP
      targetPort: 1883
  globalConfiguration:
    create: true
    spec:
      listeners:
        - name: mqtt
          port: 1883
          protocol: TCP

TransportServer Configuration:

apiVersion: k8s.nginx.org/v1
kind: TransportServer
metadata:
  name: mqtt-ts
  namespace: test
spec:
  ingressClassName: nginx
  listener:
    name: mqtt-1883
    protocol: TCP
  upstreams:
  - name: mqtt-1883
    service: <mqtt service name>
    port: 1883
  action:
    pass: mqtt-1883

Could you please assist with what might be missing here?

TIA!

[haywoodsh]

Hi @sheetalshet, could you please provide more details regarding the failure you experienced, like the Ingress Controller logs or Kubernetes events? As you're responding to this post, have you encountered the same errors as the users above? If you didn't find any errors in the transport server, global configuration, or in the logs, and your setup was working in another environment, you may want to consult the AKS documentation on correctly setting up the load balancer and firewall to allow incoming TCP traffic on specific ports.

[sheetalshet]

yes, now it's working. however, i can only use secure(8883) or non-secure MQTT ports (1883) at a time. if I create two TransportServer at once, none of them works. Is this expected?

[haywoodsh]

Hi @sheetalshet I noticed you were trying to use the listener name mqtt-1883 in the transport server but you named it mqtt in Global Configuration. Can you please make sure the names and protocols match and try it again?