Story (Required)

• As a release engineer trying to do a z stream release for 1.14.3, I want to release the upstream argocd-operator, so that I can refer that for the downstream builds

Background and Approach (Required)

• Update the Argo CD version that is bundled with the Operator in go.mod file
• Update the Argocd image corresponding to the Argo CD version in bundle/manifests/argocd-operator.clusterserviceversion.yaml and config/manager/kustomization.yaml
• Create a PR to the respective maintenance branch.
• If the PR looks good merge the changes.

Out of Scope

• N/A

Dependencies

• N/A

Acceptance Criteria (Mandatory)

• The Argo CD version is updated in the upstream argocd-operator and the PR is merged to the respective branch.

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.