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

managing PAC secret for MultiCluster

XMLWordPrintable

    • Pipelines Sprint Crookshank 38

      Story (Required)

      PAC is installed on Hub(Manager) Cluster and user creates a PAC pipelinerun on Hub cluster also secrets will be created in Hub Cluster and respective workloads (Pods, Taskrun) created on Spoke(worker) clusters but for private repos to clone the code we need a secret (which contains credentials) but those credentials won;t be available on spoke cluster

       

      As part of this story

      • We need to analyse how to handle such cases
      • How to ensure secret available in spoke clusters so that pod can make use of that
      • Its not just pac case but a general scneario where we need to get an access to secret(contains PAT) to do the clone operation for Private repos

       

      Discussion Doc: https://docs.google.com/document/d/1Y6QPfsdpHgzgRBQ4zFWG18I2N9XkU57BONoG6RiWsbM/edit?tab=t.zb9g0b7h3zra#heading=h.brkf26euphqd

       

      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

              rh-ee-zashaikh Zaki Shaikh
              sashture Savita .
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: