Story (Required)

In order to deprecate kam and remove the code, we need to remove it from the  midstream:  https://gitlab.cee.redhat.com/gitops-cpaas-midstream/gitops-midstream-repos 

Background (Required)

<Describes the context or background related to this story>

Out of scope

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

Approach (Required)

• make a PR to midstream repo** to remove kam code from...
  • [kam delivery container and kam RPM in upstream sources file|https://gitlab.cee.redhat.com/gitops-cpaas-midstream/gitops-midstream-repos/-/blob/gitops-1.12-rhel-8/upstream_sources.yaml?ref_type=heads ]
  • remove kam delivery container https://gitlab.cee.redhat.com/gitops-cpaas-midstream/gitops-midstream-repos/-/tree/gitops-1.12-rhel-8/distgit/containers/openshift-gitops-kam-delivery?ref_type=heads 
  • remove kam rpm https://gitlab.cee.redhat.com/gitops-cpaas-midstream/gitops-midstream-repos/-/tree/gitops-1.12-rhel-8/distgit/rpms/openshift-gitops-kam?ref_type=heads 

• • only for the version that it will be removed in- the 1.12 branch links used above here are only for reference)

    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