Skip to content

Conversation

@sarevalo2002
Copy link
Contributor

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):

  • Added alb.ingress.kubernetes.io/jwt-validation annotation to support JWT validation
  • Added buildSDKJwtValidationConfig to transform ingress model config to SDK config
  • Added buildJwtValidationAction to transform enhanced backend model to ingress model config
  • Added buildJwtValidationConfig to parse annotation into enhanced backend model
    • This includes some very minor client-side validation for known required values for faster feedback
  • Updated ingress e2e test with JWT validation case
  • Updated documentation with JWT validation usage and example

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
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

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

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 13, 2025
@k8s-ci-robot
Copy link
Contributor

Hi @sarevalo2002. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@k8s-ci-robot k8s-ci-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Nov 13, 2025
@zac-nixon
Copy link
Collaborator

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 13, 2025
@zac-nixon zac-nixon merged commit e17fc30 into kubernetes-sigs:main Nov 13, 2025
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants