Aws-load-balancer-controller: Ingress with routes always falls back to default rule.

[ishaannarang]

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ingress
namespace: default
annotations:
alb.ingress.kubernetes.io/scheme: internet-facing
alb.ingress.kubernetes.io/subnets: subnet-1, subnet-2
alb.ingress.kubernetes.io/security-groups: sg-1
alb.ingress.kubernetes.io/tags: Environment=dev,Team=test
spec:
rules:

• host: abc.net
  http:
  paths:
  
  
  
  • path: /
    
    backend:
    
    serviceName: jena-fu
    
    servicePort: 3030
  
  
  • path: /svc2
    
    backend:
    
    serviceName: svc2
    
    servicePort: 8080
  
  

When I hit abc.net, I am able to access jena-fu service, but when I hit abc.net/svc2, I am not able to access svc2. I tried /svc2* as well, same result.

[chrisckchang]

i'm also seeing this behavior. it looks as though the first path + service specified takes priority and subsequent services are unaccessible.

[zijadmop]

Have the same issue, but with host based routing on internal ALB. As soon as I remove the path part from ALB using AWS console, everything works properly.

[kevinsookocheff-wf]

@ishaannarang The list of paths are additive. The first path that is found in your list that matches will be used for your route. If you change the order of paths it will work.

[bigkraig]

@ishaannarang please confirm if swapping the paths solves your problem

[ishaannarang]

it worked !!