Closed esteban1983cl closed 1 year ago
You have to add group.name annotation like this
alb.ingress.kubernetes.io/group.name: 'sample'
alb.ingress.kubernetes.io/group.order: '10'
alb.ingress.kubernetes.io/group.name: 'sample'
alb.ingress.kubernetes.io/group.order: '20'
alb.ingress.kubernetes.io/group.name: 'sample'
alb.ingress.kubernetes.io/group.order: '30'
Hi @riita10069 it doesn't work :(
@riita10069, you could specify group name via IngressClassParams as well. @esteban1983cl, for the ingress you see 404 response, could you make sure the backend service exists in your namespace. Controller adds a 404 rule if it is unable to find the backend service - you could verify this from the controller logs.
Hi everyone, for future googlers, it's necessary add the follow annotation by ingress for handle differents ingress and one ALB
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
annotations:
external-dns.alpha.kubernetes.io/set-identifier: "ops"
external-dns.alpha.kubernetes.io/aws-weight: "1"
alb.ingress.kubernetes.io/group.order: '20'
alb.ingress.kubernetes.io/group.name: 'eks-ops-private'
alb.ingress.kubernetes.io/ssl-redirect: '443'
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
alb.ingress.kubernetes.io/healthcheck-path: /login
Hi everyone, for future googlers, it's necessary add the follow annotation by ingress for handle differents ingress and one ALB
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
annotations: external-dns.alpha.kubernetes.io/set-identifier: "ops" external-dns.alpha.kubernetes.io/aws-weight: "1" alb.ingress.kubernetes.io/group.order: '20' alb.ingress.kubernetes.io/group.name: 'eks-ops-private' alb.ingress.kubernetes.io/ssl-redirect: '443' alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]' alb.ingress.kubernetes.io/healthcheck-path: /login
This resolved the issue for me. I was not defining alb.ingress.kubernetes.io/listen-ports in my other ingress group members and as a result the rules were getting deleted.
I'm closing this issue as for now, please feel free to reach out or reopen if you have any questions. Thanks.
Describe the bug I want configure multiple ingress using one ALB using group.name and group.order annotations, the first ingress works perfectly but when I want add other ingress I get 404 response.
Steps to reproduce 1.- Configure IAM Role with service account in kubernetes with proper permissions. 2.- Install application load balancer controller using helm (Configured IngressClass and ingressClassParams)
3.- Deploy ingresses and services with NodePort configuration.
curl -IL https://bookstack.ops.example.com returns a 404 response code the dns names are registered using external-dns addon
Expected outcome I need that ALB supports theses additionals host names. Unable to see them aws console, only I see the first one.
Environment
Additional Context: N/A