Inclusion of configuration parameter "startingDeadlineSeconds" in TektonConfig

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