EKS Automode - cant specify header attributes

[jcuribe]

• Bug Description
  EKS Cluster with automode enabled v1.32.
  When I create or update an ingress and use annotation like the following:
  alb.ingress.kubernetes.io/listener-attributes.HTTPS-443: routing.http.response.strict_transport_security.header_value=max-age=600; includeSubDomains; preload
  the corresponding load-balancer is correctly created or updated but the listner is not updated.

• Steps to Reproduce
  create a EKS cluster with auto mode enabled
  create a svc and corresponding ingress , add any anotation under alb.ingress.kubernetes.io/listener-attributes.HTTPS-443. for example alb.ingress.kubernetes.io/listener-attributes.HTTPS-443: routing.http.response.strict_transport_security.header_value=max-age=600; includeSubDomains; preload

• Expected Behavior
  under the correpoinding HTTPS-443 listener the header should be added

• Environment
  EKS version 1.32 automode enabled

[wweiwei-li]

Hey, did you see any controller logs with error messages ?

[jcuribe]

really difficult to debug. when you have auto mode enabled in cluster the controller is that normally manages the alb is "managed" so no way to look at logs.

I searched in cloudtrail but did not see anything with regard to the load balancer listener. so my guess is that I'm missing something or its not supported.

[oliviassss]

Hi @jcuribe, the EKS Auto mode LBC hasn't supported this feature yet. @M00nF1sh is doing some refactoring work for the code base, after that's done we should have the EKS auto mode LBC supporting the latest version of open-source LBC.