change api v1alpha2 to v1 for old dbs

Signed-off-by: SK Ali Arman <[email protected]>

docs/guides/elasticsearch/autoscaler/compute/combined/index.md

@@ -48,7 +48,7 @@ Here, we are going to deploy an `Elasticsearch` in combined cluster mode using a
 In this section, we are going to deploy an Elasticsearch combined cluster with ElasticsearchVersion `xpack-8.11.1`.  Then, in the next section, we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create,
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-combined

docs/guides/elasticsearch/autoscaler/compute/combined/yamls/es-combined.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-combined

docs/guides/elasticsearch/autoscaler/compute/topology/index.md

@@ -48,7 +48,7 @@ Here, we are going to deploy an `Elasticsearch` topology cluster using a support
 In this section, we are going to deploy an Elasticsearch topology with ElasticsearchVersion `opensearch-2.8.0`. Then, in the next section we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create,
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-topology

docs/guides/elasticsearch/autoscaler/compute/topology/yamls/es-topology.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-topology

docs/guides/elasticsearch/autoscaler/storage/combined/index.md

@@ -61,7 +61,7 @@ Now, we are going to deploy a `Elasticsearch` combined cluster using a supported
 In this section, we are going to deploy an Elasticsearch combined cluster with version `xpack-8.11.1`.  Then, in the next section we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create,
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-combined

docs/guides/elasticsearch/autoscaler/storage/combined/yamls/es-combined.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-combined

docs/guides/elasticsearch/autoscaler/storage/topology/index.md

@@ -61,7 +61,7 @@ Now, we are going to deploy a `Elasticsearch` topology cluster using a supported
 In this section, we are going to deploy a Elasticsearch topology cluster with version `xpack-8.11.1`.  Then, in the next section we will set up autoscaling for this database using `ElasticsearchAutoscaler` CRD. Below is the YAML of the `Elasticsearch` CR that we are going to create,
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-topology

docs/guides/elasticsearch/autoscaler/storage/topology/yamls/es-topology.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-topology

docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-2.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-demo-2

docs/guides/elasticsearch/backup/auto-backup/examples/es-demo-3.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-demo-3

docs/guides/elasticsearch/backup/auto-backup/examples/es-demo.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-demo

docs/guides/elasticsearch/backup/auto-backup/index.md

@@ -148,7 +148,7 @@ secret/gcs-secret created
 Now, we are going to create an Elasticsearch CRO in `demo` namespace. Below is the YAML of the Elasticsearch object that we are going to create,
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-demo
@@ -325,7 +325,7 @@ secret/gcs-secret created
 Now, we are going to create an Elasticsearch CRO in `demo-2` namespace. Below is the YAML of the Elasticsearch object that we are going to create,
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-demo-2
@@ -504,7 +504,7 @@ secret/gcs-secret created
 Now, we are going to create an Elasticsearch CRO in `demo-3` namespace. Below is the YAML of the Elasticsearch object that we are going to create,
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-demo-3

docs/guides/elasticsearch/backup/customization/examples/elasticsearch.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: sample-elasticsearch

docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/init_sample.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: init-sample

docs/guides/elasticsearch/backup/kubedb/examples/elasticsearch/sample_es.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: sample-es

docs/guides/elasticsearch/backup/kubedb/index.md

@@ -48,7 +48,7 @@ In this section, we are going to deploy an Elasticsearch database using KubeDB.
 At first, let's deploy a sample Elasticsearch database. Below is the YAML of a sample Elasticsearch crd that we are going to create for this tutorial:
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: sample-es
@@ -828,7 +828,7 @@ Now, we are going to deploy an Elasticsearch into `restored` namespace. We are g
 Here, is the YAML of the Elasticsearch object that we are going to create,
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: init-sample

docs/guides/elasticsearch/cli/cli.md

@@ -54,7 +54,7 @@ To get YAML of an object, use `--output=yaml` flag.
 
 ```yaml
 $ kubectl get elasticsearch elasticsearch-demo --output=yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   creationTimestamp: 2018-10-08T14:22:19Z
@@ -64,7 +64,7 @@ metadata:
   name: elasticsearch-demo
   namespace: demo
   resourceVersion: "51660"
-  selfLink: /apis/kubedb.com/v1alpha2/namespaces/default/elasticsearches/elasticsearch-demo
+  selfLink: /apis/kubedb.com/v1/namespaces/default/elasticsearches/elasticsearch-demo
   uid: 90a54c9e-cb05-11e8-8d51-9eed48c5e947
 spec:
   authSecret:

docs/guides/elasticsearch/clustering/combined-cluster/index.md

@@ -40,7 +40,7 @@ demo                 Active   9s
 Here, we are going to create a standalone (ie. `replicas: 1`) Elasticsearch cluster. We will use the Elasticsearch image provided by the Opendistro (`opensearch-2.8.0`) for this demo. To learn more about Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md).
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-standalone
@@ -158,7 +158,7 @@ $ curl -XGET -k -u 'admin:V,YY1.qXxoAch9)B' "https://localhost:9200/_cluster/hea
 Here, we are going to create a multi-node (say `replicas: 3`) Elasticsearch cluster. We will use the Elasticsearch image provided by the Opendistro (`opensearch-2.8.0`) for this demo. To learn more about Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md).
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-multinode

docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-multinode.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-multinode

docs/guides/elasticsearch/clustering/combined-cluster/yamls/es-standalone.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-standalone

docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/index.md

@@ -54,7 +54,7 @@ Here, we use `linode-block-storage` as StorageClass in this demo.
 We are going to create a Elasticsearch Hot-Warm-Cold cluster in topology mode. Our cluster will be consist of 2 master nodes, 2 ingest nodes, 1 data content node, 3 data hot nodes, 2 data warm node, and 2 data cold nodes. Here, we are using Elasticsearch version (`xpack-8.11.1`) of ElasticStack distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md).
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-cluster
@@ -158,7 +158,7 @@ Name:         es-cluster
 Namespace:    demo
 Labels:       <none>
 Annotations:  <none>
-API Version:  kubedb.com/v1alpha2
+API Version:  kubedb.com/v1
 Kind:         Elasticsearch
 Metadata:
   Creation Timestamp:  2022-03-14T06:33:20Z

docs/guides/elasticsearch/clustering/topology-cluster/hot-warm-cold-cluster/yamls/es-cluster.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-cluster

docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/index.md

@@ -50,7 +50,7 @@ Here, we have `standard` StorageClass in our cluster from [Local Path Provisione
 We are going to create a Elasticsearch Simple Dedicated Cluster in topology mode. Our cluster will be consist of 2 master nodes, 3 data nodes, 2 ingest nodes. Here, we are using Elasticsearch version ( `xpack-8.11.1` ) of SearchGuard distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md).
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-cluster
@@ -128,7 +128,7 @@ Name:         es-cluster
 Namespace:    demo
 Labels:       <none>
 Annotations:  <none>
-API Version:  kubedb.com/v1alpha2
+API Version:  kubedb.com/v1
 Kind:         Elasticsearch
 Metadata:
   Creation Timestamp:  2022-04-07T09:48:51Z

docs/guides/elasticsearch/clustering/topology-cluster/simple-dedicated-cluster/yamls/es-cluster.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-cluster

docs/guides/elasticsearch/concepts/appbinding/index.md

@@ -34,7 +34,7 @@ kind: AppBinding
 metadata:
   annotations:
     kubectl.kubernetes.io/last-applied-configuration: |
-      {"apiVersion":"kubedb.com/v1alpha2","kind":"Elasticsearch","metadata":{"annotations":{},"name":"es-quickstart","namespace":"demo"},"spec":{"enableSSL":true,"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","deletionPolicy":"Delete","version":"xpack-8.2.3"}}
+      {"apiVersion":"kubedb.com/v1","kind":"Elasticsearch","metadata":{"annotations":{},"name":"es-quickstart","namespace":"demo"},"spec":{"enableSSL":true,"replicas":3,"storage":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"1Gi"}},"storageClassName":"standard"},"storageType":"Durable","deletionPolicy":"Delete","version":"xpack-8.2.3"}}
   creationTimestamp: "2022-12-29T05:03:33Z"
   generation: 1
   labels:
@@ -45,7 +45,7 @@ metadata:
   name: es-quickstart
   namespace: demo
   ownerReferences:
-    - apiVersion: kubedb.com/v1alpha2
+    - apiVersion: kubedb.com/v1
       blockOwnerDeletion: true
       controller: true
       kind: Elasticsearch

docs/guides/elasticsearch/concepts/elasticsearch/index.md

@@ -23,7 +23,7 @@ section_menu_id: guides
 As with all other Kubernetes objects, an Elasticsearch needs `apiVersion`, `kind`, and `metadata` fields. It also needs a `.spec` section. Below is an example Elasticsearch object.
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: myes

docs/guides/elasticsearch/configuration/combined-cluster/index.md

@@ -95,7 +95,7 @@ Now that the config secret is created, it needs to be mention in the [Elasticsea
 
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-multinode

docs/guides/elasticsearch/configuration/combined-cluster/yamls/es-combined.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-multinode

docs/guides/elasticsearch/configuration/jvm-options/index.md

@@ -75,7 +75,7 @@ secret/es-custom-config created
 Now Deploy the Elasticsearch Cluster with the custom `jvm.options` file:
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-test

docs/guides/elasticsearch/configuration/jvm-options/yamls/elasticsearch.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-test

docs/guides/elasticsearch/configuration/overview/index.md

@@ -55,7 +55,7 @@ The `OpenDistro` security plugin has the following configuration files:
 The custom configuration files are passed via a Kubernetes secret. The **file names are the keys** of the Secret with the **file-contents as the values**. The secret name needs to be mentioned in `spec.configSecret.name` of the [Elasticsearch](/docs/guides/elasticsearch/concepts/elasticsearch/index.md) object.
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-custom-config

docs/guides/elasticsearch/configuration/topology-cluster/index.md

@@ -133,7 +133,7 @@ secret/es-custom-config created
 Now that the config secret is created, it needs to be mention in the [Elasticsearch](/docs/guides/elasticsearch/concepts/elasticsearch/index.md) object's yaml:
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-topology

docs/guides/elasticsearch/configuration/topology-cluster/yamls/es-topology.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-topology

docs/guides/elasticsearch/custom-rbac/using-custom-rbac.md

@@ -136,7 +136,7 @@ elasticsearch.kubedb.com/quick-elasticsearch created
 Below is the YAML for the Elasticsearch crd we just created.
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: quick-elasticsearch
@@ -187,7 +187,7 @@ elasticsearch.kubedb.com/quick-elasticsearch created
 Below is the YAML for the Elasticsearch crd we just created.
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: minute-elasticsearch

docs/guides/elasticsearch/elasticsearch-dashboard/kibana/index.md

@@ -50,7 +50,7 @@ Here, we have `standard` StorageClass in our cluster from [Local Path Provisione
 We are going to create a Elasticsearch Simple Dedicated Cluster in topology mode. Our cluster will be consist of 2 master nodes, 3 data nodes, 2 ingest nodes. Here, we are using Elasticsearch version (`xpack-8.2.3`) of Elasticsearch distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md).
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-cluster
@@ -128,7 +128,7 @@ Name:         es-cluster
 Namespace:    demo
 Labels:       <none>
 Annotations:  <none>
-API Version:  kubedb.com/v1alpha2
+API Version:  kubedb.com/v1
 Kind:         Elasticsearch
 Metadata:
   Creation Timestamp:  2022-06-08T11:03:43Z

docs/guides/elasticsearch/elasticsearch-dashboard/kibana/yamls/es-cluster.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: es-cluster

docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/index.md

@@ -52,7 +52,7 @@ Here, we have `standard` StorageClass in our cluster from [Local Path Provisione
 We are going to create a OpenSearch Cluster in topology mode. Our cluster will be consist of 2 master nodes, 3 data nodes, 2 ingest nodes. Here, we are using Elasticsearch version ( `opensearch-2.8.0` ) of OpenSearch distribution for this demo. To learn more about the Elasticsearch CR, visit [here](/docs/guides/elasticsearch/concepts/elasticsearch/index.md).
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: os-cluster
@@ -130,7 +130,7 @@ Name:         os-cluster
 Namespace:    demo
 Labels:       <none>
 Annotations:  <none>
-API Version:  kubedb.com/v1alpha2
+API Version:  kubedb.com/v1
 Kind:         Elasticsearch
 Metadata:
   Creation Timestamp:  2022-06-08T06:01:54Z

docs/guides/elasticsearch/elasticsearch-dashboard/opensearch-dashboards/yamls/os-cluster.yaml

@@ -1,4 +1,4 @@
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Elasticsearch
 metadata:
   name: os-cluster

docs/guides/elasticsearch/monitoring/overview.md

@@ -47,7 +47,7 @@ In order to enable monitoring for a database, you have to configure `spec.monito
 A sample YAML for Redis crd with `spec.monitor` section configured to enable monitoring with [Prometheus operator](https://github.com/prometheus-operator/prometheus-operator) is shown below.
 
 ```yaml
-apiVersion: kubedb.com/v1alpha2
+apiVersion: kubedb.com/v1
 kind: Redis
 metadata:
   name: sample-redis