Add running_pod_log_lines config option to KubernetesExecutor#69301
Draft
jason810496 wants to merge 1 commit into
Draft
Add running_pod_log_lines config option to KubernetesExecutor#69301jason810496 wants to merge 1 commit into
jason810496 wants to merge 1 commit into
Conversation
The number of log lines fetched from a running task's pod was a hardcoded class constant (100), so deployments could not tune how much of a running task's log is visible in the UI without patching the executor.
This was referenced Jul 3, 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.
part of the streaming task log series
Why
The number of pod log lines fetched for a running task is a hardcoded class constant (
RUNNING_POD_LOG_LINES = 100), so deployments cannot tune how much of a running task's log the UI shows.What
[kubernetes_executor] running_pod_log_linesconfig option (default100, the previous hardcoded value).KubernetesExecutor.__init__reads it through the team-aware executor conf, shadowing the class default per instance.Was generative AI tooling used to co-author this PR?