Requeue and Retry Tektoncd Pipeline upgrade if there are active TaskRuns
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
Feature request
The operator should make sure that there are no active TaskRuns before carrying out a Tektoncd Pipeline upgrade.
Use case
Internal changes in Tektoncd Pipeline could break active TaskRuns after an upgrade. For example: If we add/filtering of Pods in Pipelines controller, Pods created by an older version of Pipelines controller will not be visible to a newer Pipelines controller.
To ensure, that there are not unpleasant surprises (eg: TaskRun failure during a Pipeline Upgrade), we need to make sure that the operator waits and retries an upgrade if there are active TaskRuns.
Ref:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Tektoncd Pipeline issue 4398 and tracing the operator's Pipeline upgrade path and TaskRun handling. Define done as deferring and retrying an upgrade while TaskRuns are active, then proceeding once none remain, with coverage for both active and cleared cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100