aws: Update LBC to v2.17.1

[hakman]

/cc @rifelpet @justinsb

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign zetaab for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[rifelpet]

/lgtm

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[hakman]

/test pull-kops-e2e-k8s-gce-cilium

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[rifelpet]

One of the tests is consistently failing because we need to update the IAM policy to use the Null condition for CreateTargetGroup like in the example

https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/docs/install/iam_policy.json

[hakman]

@rifelpet Just wanted to see that the clusters validates consistently and most tests run.
I am thinking it may be better to exclude the kube-system namespace for LB webhooks. WDYT?

[rifelpet]

None of kops' addons in kube-system need AWS load balancers. I suppose users might be installing their own applications to kube-system that might need LBs? I'm not sure how much we guarantee around that or if users would need a way to override that behavior.

[k8s-ci-robot]

@hakman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kops-e2e-aws-upgrade-k133-ko133-to-kstable-kolatest-many-addons	13a1872	link	false	/test pull-kops-e2e-aws-upgrade-k133-ko133-to-kstable-kolatest-many-addons
pull-kops-e2e-aws-load-balancer-controller	13a1872	link	true	/test pull-kops-e2e-aws-load-balancer-controller

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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-sigs/prow repository. I understand the commands that are listed here.

[hakman]

/test pull-kops-e2e-k8s-aws-amazonvpc

[rifelpet]

@hakman should we merge this as-is and fix the tests in a followup?