Story (Required)

Metrics config and Service must be used from the released manifests of Tekton chains instead of manually adding from pipeline service

Currently, when installing chains in pipeline service via operator we have to manually add config-observability and observability service for Tekton chains

• https://github.com/openshift-pipelines/pipeline-service/blob/main/operator/gitops/argocd/pipeline-service/openshift-pipelines/chains-observability-service.yaml

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

Tekton Chains did not have a service for observability and no option for configuring the observability. The story PLNSRVCE-1355 adds those missing manifests.

_Version Matrix: https://docs.openshift.com/pipelines/1.14/about/op-release-notes.html#compatibility-support-matrix_op-release-notes_

Out of scope

<Defines what is not included in this story>

• configuring metrics
• Any code change in upstream

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

• Remove manually added manifests
• Update Operator in Pipeline service with Chains Versions >= 0.17.0 (https://github.com/tektoncd/chains/releases/tag/v0.17.0)

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria  (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

• The metrics config and service manifests should come from release manifests or operator.

  Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met