fix(computing-unit-managing-service): pass AUTH_JWT_SECRET to newly created computing units#4426
Merged
Merged
Conversation
bobbai00
changed the title
AUTH_JWT_SECRET to newly created Computing UnitAUTH_JWT_SECRET to newly created Computing Unit
bobbai00
changed the title
AUTH_JWT_SECRET to newly created Computing UnitAUTH_JWT_SECRET to newly created computing units
bobbai00
approved these changes
Apr 20, 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
3 participants
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.
What changes were proposed in this PR?
Computing units are created by calling Kubernetes functions and are created in a separate namespace, in this regard they do not share other services and pods settings including environment variable. In this PR we pass
AUTH_JWT_SECRETenvironment variable previously introduced in #4388Any related issues, documentation, discussions?
Fixes #4425
How was this PR tested?
Tested using the k8s deployment
Was this PR authored or co-authored using generative AI tooling?
No