Epic Goal

By default, If a TaskRun runs longer than its timeout value, the pod associated with the TaskRun will be deleted. This means that the logs of the TaskRun are not preserved. The deletion of the TaskRun pod is necessary in order to stop TaskRun step containers from running.

We already have keep-pod-on-cancel, but this only applies when the Pipeline/Task is cancelled. We should take into account this feature-flag, and if true, we should respect it when the Pipeline/Task times-out, a.k.a. not deleting the Pod.
Use case

Why is this important?

When there is a timeout, the user might want to inspect the Pod (or at least look at the logs) to understand what happened ; especially if the user can already do this when he/she cancels the Pipeline/Task.

Scenarios

N/A

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• When keep-pod-on-cancel is set to true, a Pipeline or Task that times out shouldn't delete the Pod

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment