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

Visualizing Tekton Results on the OpenShift Web console into the GitOps operator screen.

Goals

It would benefit customers.

It's current state is that customers have to use the opc tool in order to query the Tekton Results.
https://docs.openshift.com/pipelines/1.14/records/using-tekton-results-for-openshift-pipelines-observability.html#querying-using-opc_using-tekton-results-for-openshift-pipelines-observability

Another alternative (undocummented and unsupported) is using API calls, but it requires setting Kubernetes impersonation.

Requirements

Having a way to trak the results from the OpenShift Web console.

Out of scope

Using additional CLIs or Kubernetes impersonation.

Assumptions

I'm assuming we would need to be having a results resource type in OpenShift in order to be able to list it from the OpenShift web console.

Documentation Considerations

https://docs.openshift.com/pipelines/1.14/records/using-tekton-results-for-openshift-pipelines-observability.html#querying-using-opc_using-tekton-results-for-openshift-pipelines-observability

What does success look like?

Updates to current documentation.

Related Architecture/Technical Documents

https://docs.openshift.com/pipelines/1.14/records/using-tekton-results-for-openshift-pipelines-observability.html#querying-using-opc_using-tekton-results-for-openshift-pipelines-observability

https://tekton.dev/docs/results/

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