Description of Problem

• `kam` is getting deprecated with v1.15 but its deployment exists after upgrade from 1.14.2

Additional Info

• N/A

Problem Reproduction

• Install 1.14.2 from v1.15 catalog source
• Upgrade to 1.15
• Observe pd for `kam` up and running

Reproducibility

• Always

Prerequisites/Environment

• OCP 4.17, GitOps v1.15.0-7

Steps to Reproduce

• Refer to `Problem Reproduction`

Expected Results

• `kam` pod does not exists after the upgrade or with direct installation

Actual Results

• `kam` pod exists after the upgrade

Problem Analysis

• <Completed by engineering team as part of the triage/refinement process>

Root Cause

• <What is the root cause of the problem? Or, why is it not a bug?>

Workaround (If Possible)

• <Are there any workarounds we can provide to the customers?>

Fix Approaches

• <If we decide to fix this bug, how will we do it?>

Acceptance Criteria

• ...

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.