kanisterio/kanister

Improve ouput log parsing for long-running operations

Open

#3,583 opened on Jul 31, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (178 forks)auto 404
acceptedhelp wanted

Repository metrics

Stars
 (883 stars)
PR merge metrics
 (PR metrics pending)

Description

Follow up to https://github.com/kanisterio/kanister/issues/1622 and https://github.com/kanisterio/kanister/pull/2972

Currently we stream logs from pods during execution, which might fail with timeout in case of long operation. Since we run pods to completion in KubeTask of MultiContainerRun, we only need the output once it completes. This means that apart from progress tracking we don't necessary need to stream the logs during the execution.

We can separate log parsing for progress tracking (stream during execution) and parsing for output (after pod completes) which prevents timeout issues.

Contributor guide

Research direction
Investigate the current log streaming implementation for KubeTask and MultiContainerRun, and design a separation between progress tracking log parsing and output log parsing to avoid timeouts.
Tech stack
go
Domain
backenddevopsinfrastructure
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60