Story (Required)

As a developer of GitOps Operator, I want to bring the upstream support to use secrets for tls data for server routes from argocd-operator into gitops operator.

Background (Required)

The support for directly embedding tls data for server route into ArgoCD CR is deprecated in upstream operator in favor of using secrets to store this sensitive data. 

Approach (Required)

• Update commit reference & ArgoCD CRDs in gitops-operator
• Add a e2e kuttl test
• Pull the change into midstream (gitlab)
• Validate the change in downstream by building a IIB

Dependencies

GITOPS-5516 & GITOPS-5517

Acceptance Criteria (Mandatory)

• Changes are pulled into downstream product code
• The downstream operator is built and validate successfully with the new change.

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