Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-8979

Introduce MultiCluster Spec field in Operator

XMLWordPrintable

    • Pipelines Sprint Pioneers 39

      Story (Required)

      As part of this story we will add a new spec field called MultiCluster and add the Required yamls, CRDs

       

      kind: TektonConfig
      metadata:
        creationTimestamp: "2025-09-24T07:47:44Z"
        finalizers:
        - tektonconfigs.operator.tekton.dev
        generation: 2
        labels:
          openshift-pipelines.tekton.dev/sa-created: "true"
          operator.tekton.dev/release-version: 1.19.3
        name: config
        resourceVersion: "24610"
        uid: e96291c5-28dd-4352-aff3-3a70f6d9bdb5
      spec:
      ...
        multiCluster:
          disabled: false
          role: hub or spoke 

       

       

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

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

      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>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      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

              sashture Savita .
              sashture Savita .
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: