Repository navigation
Configure workload resources and short-lived tokens - #77
Merged
Merged
Conversation
2 tasks done
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
1 participant
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
Use five-minute login tokens in the disposable SLO cluster and allow workload container CPU/memory limits to be set through Compose environment variables.
Why
Long stability runs need to exercise real token expiry and renewal. The existing two-CPU limit also constrains a workload with multiple producer workers feeding a reader.
Changes
auth_config.login_token_expire_time: 5min the default and bridge YDB configurations. Anonymous workloads remain supported.WORKLOAD_CPU_LIMITandWORKLOAD_MEMORY_LIMIT, retaining the existing defaults of 2 CPU and 4 GiB for current and baseline containers.deploy/so local Compose and CI use the same infrastructure.Used by ydb-js-sdk#658.
Testing
67 unit tests pass; bundle and lint pass.
Default and bridge Compose configurations validate, including overridden resource limits.
Local cluster bootstraps with both plaintext and TLS readiness checks; the JS topic workload connects using login authentication over TLS.
A 390-second JS SDK control verifies accepted token renewal on the reader and all 24 writer streams, continued traffic after the old tokens expire, and complete message reconciliation.