Copy of Develop a migration strategy for ArgoCD

[meganhicks]

After establishing svc-bip-api as VRO's first app deployable in ArgoCD, we should determine a strategy for rolling out the ArgoCD deployment option for other apps on VRO; and a strategy for deprecating use of non-ArgoCD deployments. Additionally, we should ensure the partner teams have visibility into these changes.

Acceptance criteria

1. There is a plan for deprecating use of non-ArgoCD deployments that is documented.
2. a decision on when to address Configure ArgoCD + Vault for svc-bip-api #3037
3. documentation to account for complexities in troubleshooting deployments. for example: how does one figure out which platform did the deployment (ArgoCD or non-ArgoCD)?
4. Share the plan with the team (including the enablement team) and ensure the team is aligned.
5. Any actions we are taking should not impact our partner teams

Notes about work

• related to the completion of Configure ArgoCD cut over for Prod cluster all services  #3041
• consider implementing a CODEOWNERS on va-abd-rrd-argocd-applications-vault - why: to support partner teams configuring deployments on their own apps while not disrupting affecting apps of other partners