Aws-load-balancer-controller: alb.ingress.kubernetes.io/connection-idle-timeout has no effect

[rootd00d]

I've been using this controller (1.0-beta.7) for a few weeks now, but recently ran into an issue where I needed the idle timeout to be much greater than the default 60s.

No matter what I do, setting alb.ingress.kubernetes.io/connection-idle-timeout seems to have no effect; either when provisioning new ALBs or updating existing ALBs.

Is there something I'm missing here?

  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/connection-idle-timeout: "1800"
...

[rifelpet]

Does the documentation mention a connection-idle-timeout annotation? I don't see it anywhere:

https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/master/docs/api/ingress.md

I believe you'll want the load-balancer-attributes annotation set to idle_timeout.timeout_seconds=1800

https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/8c2fbfd478a77f983afde2bb5a3ce2f06957e75d/internal/alb/lb/attributes.go#L20

[M00nF1sh]

@rifelpet is correct :D, you should use alb.ingress.kubernetes.io/load-balancer-attributes: idle_timeout.timeout_seconds=1800
Docs should be improved to include supported attributes

[rootd00d]

Thanks for following up so fast guys. I was able to get this working. Full disclosure: since it was undocumented, I had found that annotation in another issue here, which is why I was confused -- https://github.com/kubernetes-sigs/aws-alb-ingress-controller/issues/361

[lmgnid]

Hello, I am using "docker.io/amazon/aws-alb-ingress-controller:v1.1.5" and used this annotation for multi ingresses:
"alb.ingress.kubernetes.io/load-balancer-attributes: idle_timeout.timeout_seconds=300"
But not all ingresses works, in one EKS cluster, maybe the 1st ingerss/alb doesn't work, but in another EKS cluster, maybe the 3rd ingress/alb doesn't work and no rules.
Any ideas?
PS: No errors in ALB controllers though.