Promote `apiVersion: argoproj.io/v1alpha1` to `v1`

[slmingol]

Summary

We maintain a distro of ArgoCD within our company to deploy applications to our Openshift clusters. We were curious what the plans were to at some point promote the apiVersion: argoproj.io/v1alpha1 to apiVersion: argoproj.io/v1 or v1beta1 at some point?

What change you think needs making.
apiVersion: argocdproj.io/v1 or apiVersion: argocdproj.io/v1beta1

Motivation

This particular apiVersion has been set to argoproj.io/v1alpha1 for quite a while, we're just curious what the plans are around it.

Please give examples of your use case, e.g. when would you use this.

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
...

Proposal

apiVersion: argocdproj.io/v1 or apiVersion: argocdproj.io/v1beta1

How do you think this should be implemented?
apiVersion: argocdproj.io/v1 or apiVersion: argocdproj.io/v1beta1

[crenshaw-dev]

I think we'll bump it to v1 when we cut 3.0. There are some breaking changes we'll need to make. It's a good time to increment the release.

[christianh814]

I think we'll bump it to v1 when we cut 3.0. There are some breaking changes we'll need to make. It's a good time to increment the release.

Should we consider using v3? 🤔

[globart]

@crenshaw-dev 3.0 was released several months ago, any plans/updates?

[crenshaw-dev]

3.0 ended up being big enough that we didn't want a version upgrade to complicate things, so we deferred.