Annotation service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled not working on NLB

[luisamador]

What happened:
service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
The annotation above doesn't take any effect on NLBs. It doesn't matter if you are updating an existing NLB or if you are provisioning it from scratch.

What you expected to happen:
The "Cross-zone load balancing" setting enabled on the NLB.

How to reproduce it (as minimally and precisely as possible):
Just create a K8s Service resource with the following annotations:

service.beta.kubernetes.io/aws-load-balancer-type: "nlb"
service.beta.kubernetes.io/aws-load-balancer-internal: "true"
service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"

Environment:
both Kubectl and AWS EKS cluster on version v1.18.9

/kind bug

[mars64]

I think you're looking for the aws-load-balancer-controller project -- they just took over for the Ticketmaster/CoreOS ALB Ingress Controller and I think are the ones that provide the annotation you reference.

[edit]: I can at least confirm that service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true" appears to work properly via aws-load-balancer-controller

[edit x 2]: derp I was using an nlb-ip. My test is invalid, they don't provide for nlb yet.

In any case, behold:

• Add PROXY protocol support for AWS Network Load Balancers kubernetes#57250
• AWS: Network Load Balancer ignores annotations upon creation kubernetes#82595
• https://gist.github.com/mgoodness/1a2926f3b02d8e8149c224d25cc57dc1#gistcomment-3322478

What I take from this is:

• legacy provider will be fixed in 1.20
• go-forward provider (i.e. aws-load-balancer-controller) still figuring out how to take this over from in-tree

[kishorj]

Legacy cloud provider has the fix kubernetes/kubernetes#95247, and will be available in 1.20.

[nckturner]

/close

[k8s-ci-robot]

@nckturner: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.