Change:
What would you like to be : Add support for AWS NLB access log configuration via annotations. The same annotations currently supported by the ELB classic could be reused:
/sig aws
/sig cloud-provider
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/reopen
You can't reopen an issue/PR unless you authored it or you are a collaborator. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Unresolved and Closed - any plans to reopen this issue?
Also looking forward for this.
Yes, we need this. And we also need for NLB to work the following annotations:
Dear, do we plan support enable the NLB access log via annotations?
I know this issue is closed, but I'm following up to see if enabling NLB access logs via annotations is or will be supported. I'm looking to enable logs using the same annotations as in the previous comment. If this is not currently supported, what is the best way to enable the logs in the deployment? I'm looking for a way that isn't manually enabling them in the AWS console.
Please...
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This is already supported by however, there is still a known issue. You need to create the service first and then adding these lb attributes annotations later to make it work, we'll fix it.
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
is this issue. It was accidentally closed by a related MR that didn't resolve the issue (it was fixing health check annotation issues) and will hopefully be reopened soon. Edit: Fixed in Kubernetes 1.20 by

Discussion:
return nil, fmt.Errorf("error creating listener: %q", err) } } <ins> if err := c.reconcileLBAttributes(aws.StringValue(loadBalancer.LoadBalancerArn), annotations); err != nil { return nil, err } </ins> } else { // TODO: Sync internal vs non-internal