Story (Required)

This story tracks the effort involved in bringing the API upgrade to the operator-redesign branch

Upgrade ArgoCD CRD api version in argocd-operator from v1alpha1 to v1beta1.

Background (Required)

GITOPS-2473 introduced break changes in ArgoCD CRD. According to best practices, we should update CRD api version for breaking changes in CRD.

https://redhat-internal.slack.com/archives/C048WUV584F/p1688069114593959 

Out of scope

GITOPS-2473 removed .spec.dex and some of .spec.sso fields which leads to breaking user experience in ArgoCD v1alpha1 CRD. Handling that is out of scope for this story.

Approach (Required)

1. Create new API version(v1beta1) of ArgoCD CRD
2. Mark the new version as the storage version
3. Implement API version conversion: mark new version as hub & implement ConvertTo/ConvertFrom func in old version
4. Setup conversion webhook
5. Add unit/e2e tests

Refer https://book.kubebuilder.io/multiversion-tutorial/tutorial.html for details.

Acceptance Criteria (Mandatory)

1. New API version(v1beta1) should be added for ArgoCD CRD
2. Conversion of API version v1alpa1 to v1beta1 should be automatically handled

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