1. Proposed title of this feature request

Citi needs to get a build of Pipelines 1.10 on OCP 4.10.

2. What is the nature and description of the request?

Citi needs to upgrade to Pipelines 1.10 on OCP 4.10 to deliver critical features to their build pipeline. It is not possible for the customer to upgrade the cluster to 4.11/12 to get access to this operator version. These options were already discussed in detail with the Pipelines PM team and the account team and the customer.

The included 0.15 Tekton Chains support is one of the important areas. Aside from that, Citi wants to ensure that the ClusterTasks behave in a way that is still supportable by Citi. 

The following Chains features are important:

• Add labels and annotations to attestation
• Allow passing in of sha1 digests through StructuredResults 
• Bump github.com/hashicorp/vault/sdk from 0.6.2 to 0.7.0 

We already proposed to cherry-pick specific features into Pipelines 1.9. This was determined to be insufficient for Citi as they can't afford to duplicate efforts - every operator upgrade requires its own certification process. 

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

Citi has to roll out 2 new versions of core banking applications. These have been built using Tekton upstream with the equivalent version numbers to OCP Pipelines 1.10.

One of these applications needs to be rolled out and certified before Labor Day due to a subsequent change freeze in the environment.

For the LOB to roll this out, the lower and higher environments need to be verified with Pipelines 1.10. 

The impact for Citi of not having Pipelines 1.10 certified would have a significant impact on the commercial relationship with the customer as their internal customer might choose the EKS environment for future projects due to missed deadlines on the OCP environment.

4. List any affected packages or components.

OCP Pipelines 1.10