-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[feat: gw api] Add secure HTTPRoute and mutual auth support for L7 Ga… #4259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zac-nixon
reviewed
Jul 7, 2025
zac-nixon
reviewed
Jul 7, 2025
zac-nixon
reviewed
Jul 7, 2025
zac-nixon
reviewed
Jul 7, 2025
zac-nixon
reviewed
Jul 7, 2025
5da1a51
to
d2ca560
Compare
shuqz
reviewed
Jul 8, 2025
d2ca560
to
bc8f531
Compare
zac-nixon
reviewed
Jul 8, 2025
zac-nixon
reviewed
Jul 8, 2025
zac-nixon
approved these changes
Jul 8, 2025
bc8f531
to
0169f63
Compare
zac-nixon
approved these changes
Jul 8, 2025
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: shraddhabang, zac-nixon 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:
Approvers can indicate their approval by writing |
/lgtm |
/approved |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Mutual Authentication Support for Gateway API TLS
Overview
This PR adds support for Mutual Authentication (mTLS) to the AWS Load Balancer Controller's Gateway API implementation. The changes enable configuring mTLS on ALB listeners in multiple modes, enhance HTTPS route functionality, and provide comprehensive E2E tests for these new features.
Key Changes
1. Mutual Authentication Support for L7 Gateway
Added support for configuring mTLS on ALB listeners through Gateway API TLS configuration
Implemented three mTLS modes:
off
: Client certificates not requested (default behavior)passthrough
: Client certificates are requested but not verifiedverify
: Client certificates are requested and validated against a trust store (tests to be added in future PR)2. Added Default for ALPNPolicy
ALPN
policy configuration for TLS listeners with a default ofNone
3. HTTP Verifier Enhancements
4. Test Framework Improvements
VerifyListenerMutualAuthentication
to validate mTLS configuration on listenersVerifyLoadBalancerListener
to incorporate mutual authentication verificationMutualAuthenticationExpectation
struct to enable verification of mTLS settings5. New End-to-End Tests
off
andpassthrough
modesverify
mode will be added in a future PR once a trust store is created in the prow accountTesting
The PR includes comprehensive E2E tests that verify:
off
andpassthrough
modesEach test validates both the configuration application to AWS resources and the actual runtime behavior by making requests to the provisioned endpoints.
Future Work
A follow-up PR will add support for
verify
mode testing, which requires creating a trust store in the test AWS account.Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯