BREAKING: disable artifact streaming #1213
Merged
Conversation
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
Bryce-Soghigian
changed the title
Bryce-Soghigian
changed the title
tallaxes
approved these changes
Oct 9, 2025
Collaborator
tallaxes
left a comment
tallaxes
left a comment
There was a problem hiding this comment.
LGTM. Please update the description
Bryce-Soghigian
deleted the
cherry-pick-pr-1209-disable-artifact-streaming
branch
|
@Bryce-Soghigian are there any concrete plans to make Artifact Streaming configurable? My company has recently started experimenting with Karpenter on a cluster that definitely needs it enabled and it might be a blocker for our migration. |
Contributor
Author
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.
Fixes #
Description
Temporarily remove unconditional enabling of artifact streaming, until the regression in node provisioning latency is addressed and/or we introduce a way to control artifact streaming via configuration.
Does this change impact docs?
Release Note