Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-5222

Remove kam related resources managed by gitops-operator

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • 1.15.0
    • None
    • None
    • None
    • 5
    • False
    • None
    • False
    • GitOps Crimson - Sprint 3261, GitOps Crimson - Sprint 3262

      Story (Required)

      In order to deprecate kam and remove the code, we need to remove all the kam related resources from theĀ  gitops-operator code-base

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      • Removing kam the midstream repo
      • Do not remove kam code from any previous versions

      Approach (Required)

      Remove kam code from gitops-operator

      Dependencies

      • kam deprecation notice sent outĀ 

      Acceptance Criteria (Mandatory)

      • Approach above has been followed and PR's have been reviewed and merged

      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

            saumeyakatyal Saumeya Katyal
            rescott1 Regina Scott (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: