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

Remove deprecated ClusterTask from Operator

XMLWordPrintable

    • 1
    • False
    • None
    • False
    •    This patch will remove cluster task installersets creation and remove the all existing cluster task type installersets from the cluster during operator upgrade.
    • 5
    • Pipelines Sprint Crookshank 14, Pipelines Sprint Crookshank 15, Pipelines Sprint Crookshank 16, Pipelines Sprint Crookshank 17

      Story (Required)

      ClusterTasks are deprecated long back and this story focuses on removing those completely from Operator{}

      Slack Discussion : https://redhat-internal.slack.com/archives/CG5GV6CJD/p1727260756096559?thread_ts=1726147634.669579&cid=CG5GV6CJD

       

      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

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

                Created:
                Updated: