Add support for jwt validation action at the ingress level #4445
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.
Motivation
This PR adds AWS Load Balancer Controller support for the JWT validation action at the ingress level.
See documentation: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-verify-jwt.html
See launch announcement: https://aws.amazon.com/about-aws/whats-new/2025/11/application-load-balancer-jwt-verification/
Description
This implementation was implemented in a similar style as the existing authentication action (another pre-routing action type that is currently implemented at the ingress level):
alb.ingress.kubernetes.io/jwt-validationannotation to support JWT validationbuildSDKJwtValidationConfigto transform ingress model config to SDK configbuildJwtValidationActionto transform enhanced backend model to ingress model configbuildJwtValidationConfigto parse annotation into enhanced backend modelChecklist
README.md, or thedocsdirectory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯