< High-Level description of the feature ie: Executive Summary >

Goals

Downstream Jira For tracking https://github.com/tektoncd/pipeline/pull/8023

Proposed title of this feature request
Add a flag on controllers to configure resyncPeriod in openshift-pipelines

What is the nature and description of the request?

Downstream Jira For tracking https://github.com/tektoncd/pipeline/pull/8023

This should allow advanced user/cluster-admin to configure the
resyncPeriod to a value that fit their cluster instead of relying on
the default 10h one.

Why does the customer need this? (List the business requirements here)

We are heavily using OpenShift Pipeline and we see that every 10h we have many pending task. We have around 1500 Pipelines, and our goal is to reach 3000 Pipelines at the end of the year. PipelineTask are not created during 20 minutes every 10h

• Be able to tune the Tekton resync loop timeframe (here: https://github.com/knative/pkg/blob/main/controller/controller.go#L52)
• Have 12h as default value instead of 10h because the resync loop is shifting every day.

  Requirements

  Requirements	Notes	IS MVP

• • (Optional) Use Cases

< What are we making, for who, and why/what problem are we solving?>

Out of scope

<Defines what is not included in this story>

Dependencies

< Link or at least explain any known dependencies. >

Background, and strategic fit

< What does the person writing code, testing, documenting need to know? >

Assumptions

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Customer Considerations

< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

Documentation Considerations

< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >

What does success look like?

< Does this feature have doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact?>

QE Contact

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Impact

< If the feature is ordered with other work, state the impact of this feature on the other work>

Related Architecture/Technical Documents

<links>

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