Ephemeral container expiration improvements#782
Open
pditommaso wants to merge 17 commits intomasterfrom
Open
Conversation
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
Member
|
@pditommaso Can we move forward with this PR? |
# Conflicts: # src/main/groovy/io/seqera/wave/configuration/SsrfConfig.groovy # src/main/groovy/io/seqera/wave/encoder/DateTimeAdapter.groovy # src/main/groovy/io/seqera/wave/service/license/LicenseManValidator.groovy # src/main/groovy/io/seqera/wave/service/request/ContainerRequestStoreImpl.groovy # src/main/groovy/io/seqera/wave/tower/client/DescribeWorkflowResponse.groovy
Signed-off-by: munishchouhan <hrma017@gmail.com>
Signed-off-by: munishchouhan <hrma017@gmail.com>
Signed-off-by: munishchouhan <hrma017@gmail.com>
Member
relevance:Without this feature: Container tokens have a fixed TTL (36h on master). If a workflow runs longer than that, the token expires and the container becomes inaccessible — the With this feature: A background watcher checks if the workflow is still running on Tower. If it is, the token TTL gets extended automatically (up to a max of 2 days). Once the workflow finishes, the token expires normally. It's essentially a keep-alive mechanism — tokens stay valid as long as the workflow needs them, but don't linger forever. |
Signed-off-by: munishchouhan <hrma017@gmail.com>
Signed-off-by: munishchouhan <hrma017@gmail.com>
Signed-off-by: munishchouhan <hrma017@gmail.com>
Member
|
Tested locally: wave logs |
cristianrcv
approved these changes
Apr 8, 2026
Member
|
@pditommaso should we merge this pr? |
Collaborator
Author
|
let me review |
Member
|
@pditommaso please review |
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.

Summary
Ephemeral containers are accessible for a fixed period of time (a few hours) since their request.
However there are use cases (e.g. long workflow runs) that may require to be able to access such container for a longer period of time.
This PR extends the current logic so that when a container is requested by a workflow run submitted via Platform the container expiration time is extended as long as the corresponding workflow execution is running.
Test plan