Add basic aga controller e2e tests

[wweiwei-li]

Description

Test Files:

• globalaccelerator_suite_test.go - Test suite setup, checks commercial partition requirement
• service_endpoint_test.go - Service endpoint tests
• ingress_endpoint_test.go - Ingress endpoint tests
• multi_endpoint_test.go - Multiple endpoint types
• gateway_endpoint_test.go - Gateway API endpoint tests

Helper Files:

• resource_stack.go - ResourceStack for deploying/cleaning up GlobalAccelerator CRs.
• aga_verifier.go - Verification types & functions for AWS GlobalAccelerator configuration
• test_helpers.go - Helper functions for creating test resources (deployments, services, ingresses, GlobalAccelerator CRs)
• Uses ResourceStack from service/ingress/gateway packages directly for backend endpoint resources

Tests coverred:

Note: These tests require --enable-aga-tests flag to run (local testing only, not in CI). Make sure set up your local controller with https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/docs/guide/globalaccelerator/installation.md

Service Endpoint Tests (service_endpoint_test.go):
✅ IP target type lifecycle - Create, verify, update , verify traffic
✅ Instance target type scheme change - Deploy with internet-facing, change to internal, verify endpoint replacement
✅ Direct endpoint ID - Create GlobalAccelerator with direct load balancer ARN reference

Ingress Endpoint Tests (ingress_endpoint_test.go):
✅ Basic Ingress lifecycle - Create, verify configuration, traffic flow
✅ Auto-discovery - Automatically discover protocol and ports from Ingress
✅ IPV4 to DUAL_STACK migration - Migrate address type and verify dual-stack DNS
✅ Port overrides- Configure port overrides for listeners

Multi-Endpoint Tests (multi_endpoint_test.go):
✅ Service + Ingress endpoints - Multiple endpoint types in same namespace

Gateway Endpoint Tests (gateway_endpoint_test.go):
✅ ALB Gateway endpoint - Create GlobalAccelerator with ALB Gateway, verify configuration and traffic
✅ NLB Gateway endpoint - Create GlobalAccelerator with NLB Gateway, verify configuration and traffic

Checklist

• Added tests that cover your change (if possible)
• Added/modified documentation as required (such as the README.md, or the docs directory)
• Manually tested
• Made sure the title of the PR is a good description that can go into the release notes

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

• Backfilled missing tests for code in same general area 🎉
• Refactored something and made the world a better place 🌟

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: shraddhabang, wweiwei-li

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [shraddhabang,wweiwei-li]

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

[zac-nixon]

Just wondering, why are you using an array when you only use the first value?

[wweiwei-li]

You reminded me ... actually I was planning to have a test for multiple listeners and check traffic for multiple listening ports. Updated the helper and also added a multiple listener test. Should create GlobalAccelerator with two listeners on ports 80 and 443

[zac-nixon]

I don't see a test where you validate that we can support a port range e.g. ports 100 to 200.

[wweiwei-li]

Good point. I added a test for Should create GlobalAccelerator with port range 80-443

[zac-nixon]

nit: Do you have an ARN you can parse instead? If so, it makes this check more robust.

[wweiwei-li]

No, there's no ARN available in BeforeSuite.

[zac-nixon]

Does accelerator controller read the route data? If so, it would be interesting to validate that cross namespace routes work. If the accelerator controller doesn't read route data, then that test case doesn't seem necessarily.

[wweiwei-li]

Aga controller does not read route data. Also, for initial release, aga controller does not support cross namespace. So the test actually only verify that the gateway itself can be referenced and it's load balancer can be resolved.