Description of Problem

• There are a few additional rules added for resourceclaims CRDs in argocd-application-controller role in OCP 4.21. Need to verify if they are expected chnages

Additional Info

• Exact changes can be found here: https://gitlab.cee.redhat.com/gitops/operator-e2e/-/merge_requests/336/diffs#diff-content-cdcb3c319a4fe6d9666feea07280a49cb2baa96f

Problem Reproduction

• Add managed-by label to a user defined ns and observe the controller role

Reproducibility

• Always

Prerequisites/Environment

• OCP 4.21

Steps to Reproduce

• Install the operator on OCP 4.21
• Create a namespace with label argocd.argoproj.io/managed-by: openshift-gitops
• Observe openshift-gitops-argocd-application-controller role in the user defined ns

Expected Results

• Roles are same across all OCP versions

Actual Results

• Additional rules: https://gitlab.cee.redhat.com/gitops/operator-e2e/-/merge_requests/336/diffs#diff-content-cdcb3c319a4fe6d9666feea07280a49cb2baa96f

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.