-
Epic
-
Resolution: Done
-
Critical
-
None
-
Extended PipelineRun history and logs retention
-
False
-
False
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
Goal
As a DevOps engineer, I want to have access to the pipelinenruns details and logs for an abitrary extzended period (e.g. 365 days) without having to keep the pipelinerun CRs and taskrun pods on the cluster, so that don't have to burden etcd and storage with a large number of CRs and pods related to old pipelneruns.
Problem
PipelineRun logs on OpenShift are stored in the pods and the OpenShift logging stack. While this provides a storage for the logs, there are a number of issues when retrieving these logs:
- The pipeline CR and taskrun pods should be kept on the cluster in order to be able to access them and see the logs through OpenShift Web Console or Tekton CLI
- Retrieving logs requires complex Elasticsearch queries that most developers are not familiar with
- Retrieving the logs of a pipelinerun requires knowing the specific pipelinerun name while user most often knows only the pipeline name.
- It is non-trivial to find out the list of pipelineruns names for a pipeline and when they were executed
Related Work
Acceptance Criteria
- Pipeline logs and history can are accessible to a user beyond the lifetime of the PipelineRuns CR and taskrun pods, through OpenShift Web Console and Tekton CLI.
- clones
-
SRVKP-1512 R&D Extended PipelineRun and log retention
- Closed
- is incorporated by
-
SRVKP-2721 Ship Tekton Results
- Release Pending
- is related to
-
SRVKP-2628 Pipeline audit logs
- New
-
SRVKP-2650 Provide link to PipelineRun logs bucket
- New
-
SRVKP-1351 Recording PipelineRun artifacts
- To Do
- relates to
-
SRVKP-1576 Keep pipelines logs more accessible
- Closed