Story (Required)

As part of deprecating the kam CLI, we need to give notice to our customers before we remove it. 

Background (Required)

kam cli is being deprecated.

Out of scope

• Removing any of the code for kam CLI. 

Approach (Required)

• Send out a deprecation notice in the release notes for GitOps Operator v1.13.0. 
• In the documentation, any places that mention kam should have a mention of the deprecation and when to expect it. 
• In the kam repo, we should add a notice to the README about plans to deprecate the tool and the timeline for the deprecation.  

Dependencies

NA

Acceptance Criteria (Mandatory)

• all steps in Approach section have been followed
• PR's for docs have been 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