-
Story
-
Resolution: Done
-
Normal
-
None
-
devex docs #255 Mar 25-Apr 15, devex docs #255 Apr 15-May 6, devex docs #256 May 6-May 27, devex docs #257 May 27- Jun 17, devex docs #258 Jun 18- Jul 8
-
3
-
Documentation (Ref Guide, User Guide, etc.), User Experience
-
`startingDeadlineSeconds` configuration support added to pruner cron jobs via TektonConfig CR
-
---
-
---
1. What is the nature and description of the request?
- Client encountered a problem of "ExtremelyHighIndividualControlPlaneCPU" due to too many missed cronjob times for the tekton pruner cronjob within Openshift Pipelines.
The configuration parameter "startingDeadlineSeconds" in TektonConfig cannot be set.
Additionally client mentioned that they are talking about the pruner which prunes the pipelineruns after a defined time (=> keep-since: 20160). This pruner job is triggered by the cronjob.
2. Why does the customer need this? (List the business requirements here)
- Performance improvement
3. List any affected packages or components.
tekton pruner cronjob
- clones
-
SRVKP-4277 Inclusion of configuration parameter "startingDeadlineSeconds" in TektonConfig
- Verified
- documents
-
SRVKP-4277 Inclusion of configuration parameter "startingDeadlineSeconds" in TektonConfig
- Verified
- links to