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

Tutorial on how to setup MultiCluster on k8s (Kind)

XMLWordPrintable

    • Pipelines Sprint Pioneers 47

      Story (Required)

      Lets create a Tutorial to run MultiCluster on K8S

      1. tutorial

      • Bare minimal instructions
      • Deployment using tekton Operator
      • Automate installation of upstream keueue, pipeline, plugin
      • Deployment without using tekton Operator
      • Deploying upstream keueue
      • Deploying Tekton Pipeline
      • Deploying Kueue Plugin
      • Configurations related to Kueue and Tekton Pipeline which user has to handle

      2. 2nd Tutorial

      • Instructions on using ESO (External Secret Operator) to sync the workload from Hub to Spoke
      • Deployment using tekton Operator
      • Deploying ESO to sync the objects
      • Configurations related to Kueue and Tekton Pipeline which user has to handle

      3. 3rd Tutorial

      • Instructions using OCM (Open Cluster Management)
      • Deployment using tekton Operator
      • Deploy OCM to manage the workloads from Hub to Spoke
      • Configurations related to Kueue and Tekton Pipeline which user has to handle

      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

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

                Created:
                Updated: