Repository navigation
Add K8s projected volume JWT authentication support - #120
Merged
Merged
Conversation
dcherednik
approved these changes
Oct 7, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR an alternative authentication method for Aardappel using Kubernetes SA tokens (those are taken from a projected volume since the app is launched in k8s), instead of requiring static OAuth2 key files with embedded private keys.
Changes:
New *_k8s_jwt_auth config section with k8s_token_path, subject_token, and subject_token_type fields
Mutually exclusive with existing *_oauth2_file and *_static_token option
This enables authentication in k8s environments without static credentials and simplifies Aardappel deployments in new regions