feat: Update apiVersion argoproj.io/v1alpha1 to v1beta1 for ArgoCD in docs and tests

Signed-off-by: Oliver Gondža <ogondza@gmail.com>

Author: olivergondza

docs/developer-guide/development.md

@@ -129,7 +129,7 @@ For more infomation see [build operator images to test on a cluster.](https://ar
 
 Once the operator is installed, you would need to configure an ArgoCD instance that the operator would manage. The sample instance configuration is below:
 ``` yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd

docs/reference/argocd.md

@@ -60,7 +60,7 @@ This property maps directly to the `application.instanceLabelKey` field in the `
 The following example sets the default value in the `argocd-cm` ConfigMap using the `ApplicationInstanceLabelKey` property on the `ArgoCD` resource.
 
 ``` yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd

docs/usage/aggregated_roles.md

@@ -5,7 +5,7 @@ Using an aggregated cluster role enables users to easily add their own permissio
 A user can enable creation of aggregated ClusterRole by setting `argocd.spec.aggregatedClusterRoles` field to `true`.
 
 ```yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd
@@ -121,4 +121,4 @@ rules:
 
 Let's summarize this example. The `argocd-argocd-argocd-application-controller` cluster role inherits permissions from two cluster role which are `argocd-argocd-argocd-application-controller-view` for view permissions and `argocd-argocd-argocd-application-controller-admin` for admin permission. These three are operator managed. Now `argocd-argocd-argocd-application-controller-admin` inherits permissions from `my-cluster-role` which is a user defined cluster role.  
 
-For more details on aggregated cluster role, check the [documentation](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#aggregated-clusterroles).
+For more details on aggregated cluster role, check the [documentation](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#aggregated-clusterroles).

docs/usage/apps-in-any-namespace.md

@@ -15,7 +15,7 @@ In order to enable this feature, specify the namespaces where Argo CD should man
 
 ## Enable application creation in a specific namespace
 ```yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd
@@ -30,7 +30,7 @@ In this example:
 ## Enable application creation in namespaces matching a glob pattern
 
 ```yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd-wildcard-pattern
@@ -45,7 +45,7 @@ In this example:
 ## Enable application creation in all namespaces
 
 ```yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd-all-namespaces

docs/usage/basics.md

@@ -5,7 +5,7 @@ See the [ArgoCD Reference][argocd_reference] for the full list of properties and
 The following example shows the most minimal valid manifest to create a new Argo CD cluster with the default configuration.
 
 ```yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd

docs/usage/config_management_2.0.md

@@ -28,7 +28,7 @@ data:
       allowConcurrency: true
       lockRepo: true
 ---
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd

docs/usage/custom_roles.md

@@ -50,7 +50,7 @@ as needed and have them applied across all cluster scoped instances. For example
 These customized ClusterRoles need to be created and referred in ClusterRoleBinding by admin. A user can disable creation of default ClusterRoles by setting `ArgoCD.Spec.DefaultClusterScopedRoleDisabled` field to `true`.
 
 ```yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd
@@ -60,4 +60,4 @@ spec:
   defaultClusterScopedRoleDisabled: true
 ```
 
-When `defaultClusterScopedRoleDisabled` is `true`, the default ClusterRole/ClusterRoleBindings for the Argo CD instance will not be created, and the administrative user is free to create and customize these independent of the operator. The field can later be set to `false`, to recreate these resources, if needed.
+When `defaultClusterScopedRoleDisabled` is `true`, the default ClusterRole/ClusterRoleBindings for the Argo CD instance will not be created, and the administrative user is free to create and customize these independent of the operator. The field can later be set to `false`, to recreate these resources, if needed.

docs/usage/customization.md

@@ -7,7 +7,7 @@ See [upstream documentation](https://argo-cd.readthedocs.io/en/stable/operator-m
 Both init containers and volumes can be added to the repo server using the `ArgoCD` custom resource
 
 ```yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: argocd-sample

docs/usage/dex.md

@@ -25,7 +25,7 @@ Dex configuration has moved to `.spec.sso` in release v0.4.0. Dex can be enabled
 An example of correctly configured dex would look as follows:
 
 ```yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd
@@ -43,7 +43,7 @@ The below section describes how to configure Argo CD SSO using OpenShift connect
 The `openShiftOAuth` property can be used to trigger the operator to auto configure the built-in OpenShift OAuth server. The `groups` property is used to mandate users to be part of one or all the groups in the groups list. The RBAC `Policy` property is used to give the admin role in the Argo CD cluster to users in the OpenShift `cluster-admins` group.
 
 ``` yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd
@@ -88,7 +88,7 @@ You will very likely want to restrict logins to one or more GitHub organization.
 `connectors.config.orgs` list, add one or more GitHub organizations. Any member of the org will then be able to login to Argo CD to perform management tasks.
 
 ``` yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd
@@ -122,7 +122,7 @@ The below section describes how to configure Argo CD's Dex to accept authenticat
 In the `sso.dex.env` key, add the environment variable as shown in the [example manifests for authenticating against Argo CD's Dex](https://argoproj.github.io/argo-workflows/argo-server-sso-argocd/#example-manifests-for-authenticating-against-argo-cds-dex-kustomize).
 
 ``` yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd

docs/usage/extra-config.md

@@ -18,7 +18,7 @@ When `ExtraConfig` is set, the entries specified are reconciled to the live Argo
 ## Example
 
 ```yaml
-apiVersion: argoproj.io/v1alpha1
+apiVersion: argoproj.io/v1beta1
 kind: ArgoCD
 metadata:
   name: example-argocd