Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-4277

Inclusion of configuration parameter "startingDeadlineSeconds" in TektonConfig

XMLWordPrintable

    • 1
    • False
    • None
    • False
    • `startingDeadlineSeconds` configuration support added to pruner cron jobs via TektonConfig CR
    • Pipelines Sprint TekShift 1, Pipelines Sprint TekShift 2, Pipelines Sprint TekShift 3, Pipelines Sprint TekShift 4, Pipelines Sprint TekShift 5, Pipelines Sprint TekShift 6

      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

              jkandasa-rh Jeeva Kandasamy
              rhn-support-dtambat Darshan Tambat
              Piyush Garg Piyush Garg
              Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: