feat(eks-v2-alpha): pass additional helm chart values to aws-load-balancer-controller

[aemada-aws]

Issue # (if applicable)

Reason for this change

Currently passing in additional value to ALB helm chart is not supported.
List of supported values can be verified from https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/helm/aws-load-balancer-controller/values.yaml#L199.

This brings a feature in v1 that is missing in v2. See #34077 for original PR.

Note: This intentionally uses a JSON instead of strong typing all the values for the HelmChart because there are so many options to maintain. In EKS V1, only enableWaf and enableWafv2 were added as a response to the original issue, without allowing any other option which is perhaps not the best decision since the HelmChart supports all options as JSON instead of strong typing.

See https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/helm/aws-load-balancer-controller/values.yaml for the allowed values.

Description of changes

Added additionalHelmChartValues to AlbController properties

Describe any new or updated permissions being added

None

Description of how you validated changes

Integ + unit test

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results	24 ran	24 passed

Test	Result
No test annotations available

• View Security Guardian Results

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results with resolved templates	24 ran	24 passed

Test	Result
No test annotations available

• View Security Guardian Results with resolved templates

[abidhasan-aws]

LGTM

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

✅ The pull request has been merged at 34dcb68

This pull request spent 58 minutes 28 seconds in the queue, including 43 minutes 20 seconds running CI.
The checks were run in-place.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • feat(eks-v2-alpha): pass additional helm chart values to aws-load-balancer-controller #36754
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • feat(eks-v2-alpha): pass additional helm chart values to aws-load-balancer-controller #36754
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.