services with more than 1 ports issues

[Rockawear]

Hi,
Does VirtualServer & VirtualServerRoutes handle services with two ports or more? I'm seeing issues where I set two upstream with the same service name but a different port. It doesn't work it's complaining about duplicate upstream. The services is pointing at the same container pod. Any help is appreciated.

apiVersion: k8s.nginx.org/v1
kind: VirtualServer
metadata:
  name: virtual-server
spec:
  host: virtual-server.example.com
  tls:
    secret: virtual-server-route-tls-grpc-secret
  routes:
  - path: "/helloworld.Greeter"
    route: virtual-server-route
  - path: "/backend1/test"
    route: virtual-server-route
---
apiVersion: k8s.nginx.org/v1
kind: VirtualServerRoute
metadata:
  name: virtual-server-route
spec:
  host: virtual-server.example.com
  upstreams:
  - name: backendgrpc
    service: backend
    port: 50051
    type: grpc
  - name: backendhttp
    service: backend
    port: 80
   type: http
  subroutes:
  - path: "/helloworld.Greeter"
    action:
      pass: backendgrpc
  - path: "/backend1/test"
    action:
      pass: backendhttp

[Rockawear]

So far the only way I'm able to go around it is by creating two VirtualServerRoute for each service rather than mixing them.

[shaun-nx]

Hi @Rockawear can you please provide us with the log output from your Ingress Controller pod as well as the output of your NGINX configuration files? These will help us better debug the error you are seeing.

You can get your log output with this command:

kubectl logs <ingress-controller-pod-name> -n <ingress-controller-namespace>

To get your full NGINX config, you can run this command:

kubectl exec <ingress-controller-pod-name> -n <ingress-controller-namespace> -it  -- nginx -T

[shaun-nx]

Hi @Rockawear

I'm able to go around it is by creating two VirtualServerRoute for each service rather than mixing them.

This is exactly the way you want to use VirtualServerRoutes.
When using a VirtualServerRoute with a VirutalServer, each of your path and route entries must point to their own VirutalServerRoute, as the path defined in the VirtualServer must match the prefix of each subroute set in the respective VirtualServerRoute

Details about subroute are in our docs here

[Rockawear]

Hi @shaun-nx,
My apologies for the late response. Yeah, it works fine with VirtualServerRoute for each service; however, mixed seems to work fine if not the same service. If it's considered a bug, I can provide more details as you have asked in your first response. Otherwise, I would consider this no longer an issue for me.

[vepatel]

closing as query is resolved