-
Story
-
Resolution: Done
-
Normal
-
None
-
None
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
- clones
-
GITOPS-4592 Remove kam from gitlab midstream
- Closed