Prepare for release 3.4.22-v6 (#844)

* Prepare for release 3.4.22-v6 ProductLine: Stash Release: v2021.03.08 Release-tracker: stashed/CHANGELOG#29 Signed-off-by: 1gtm <1gtm@appscode.com> * Update mongo version Signed-off-by: Tamal Saha <tamal@appscode.com> Co-authored-by: Tamal Saha <tamal@appscode.com>
stashed · Mar 8, 2021 · cb42eb6 · cb42eb6
1 parent bf77539
commit cb42eb6
Show file tree

Hide file tree

Showing 52 changed files with 469 additions and 161 deletions.
diff --git a/charts/stash-mongodb/Chart.yaml b/charts/stash-mongodb/Chart.yaml
@@ -1,8 +1,8 @@
 apiVersion: v1
 description: 'stash-mongodb - MongoDB database plugin for Stash by AppsCode'
 name: stash-mongodb
-version: 3.4.22-v5
-appVersion: 3.4.22-v5
+version: 3.4.22-v6
+appVersion: 3.4.22-v6
 home: https://stash.run
 icon: https://cdn.appscode.com/images/products/stash/addons/mongodb-stash-addon.png
 sources:

diff --git a/charts/stash-mongodb/README.md b/charts/stash-mongodb/README.md
@@ -7,7 +7,7 @@
 ```console
 $ helm repo add appscode https://charts.appscode.com/stable/
 $ helm repo update
-$ helm install stash-mongodb-3.4.22-v5 appscode/stash-mongodb -n kube-system --version=3.4.22-v5
+$ helm install stash-mongodb-3.4.22-v6 appscode/stash-mongodb -n kube-system --version=3.4.22-v6
 ```
 
 ## Introduction
@@ -20,10 +20,10 @@ This chart deploys necessary `Function` and `Task` definition to backup or resto
 
 ## Installing the Chart
 
-To install the chart with the release name `stash-mongodb-3.4.22-v5`:
+To install the chart with the release name `stash-mongodb-3.4.22-v6`:
 
 ```console
-$ helm install stash-mongodb-3.4.22-v5 appscode/stash-mongodb -n kube-system --version=3.4.22-v5
+$ helm install stash-mongodb-3.4.22-v6 appscode/stash-mongodb -n kube-system --version=3.4.22-v6
 ```
 
 The command deploys necessary `Function` and `Task` definition to backup or restore MongoDB 3.4.22 using Stash on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
@@ -32,10 +32,10 @@ The command deploys necessary `Function` and `Task` definition to backup or rest
 
 ## Uninstalling the Chart
 
-To uninstall/delete the `stash-mongodb-3.4.22-v5`:
+To uninstall/delete the `stash-mongodb-3.4.22-v6`:
 
 ```console
-$ helm delete stash-mongodb-3.4.22-v5 -n kube-system
+$ helm delete stash-mongodb-3.4.22-v6 -n kube-system
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -50,7 +50,7 @@ The following table lists the configurable parameters of the `stash-mongodb` cha
 | fullnameOverride | Overrides fullname template                                                                                                   | `""`            |
 | image.registry   | Docker registry used to pull MongoDB addon image                                                                              | `stashed`       |
 | image.repository | Docker image used to backup/restore MongoDB database                                                                          | `stash-mongodb` |
-| image.tag        | Tag of the image that is used to backup/restore MongoDB database. This is usually same as the database version it can backup. | `3.4.22-v5`     |
+| image.tag        | Tag of the image that is used to backup/restore MongoDB database. This is usually same as the database version it can backup. | `3.4.22-v6`     |
 | backup.args      | Arguments to pass to `mongodump` command during backup process                                                                | `""`            |
 | restore.args     | Arguments to pass to `mongorestore` command during restore process                                                            | `""`            |
 | maxConcurrency   | Maximum concurrency to perform backup or restore tasks                                                                        | `3`             |
@@ -60,12 +60,12 @@ The following table lists the configurable parameters of the `stash-mongodb` cha
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example:
 
 ```console
-$ helm install stash-mongodb-3.4.22-v5 appscode/stash-mongodb -n kube-system --version=3.4.22-v5 --set image.registry=stashed
+$ helm install stash-mongodb-3.4.22-v6 appscode/stash-mongodb -n kube-system --version=3.4.22-v6 --set image.registry=stashed
 ```
 
 Alternatively, a YAML file that specifies the values for the parameters can be provided while
 installing the chart. For example:
 
 ```console
-$ helm install stash-mongodb-3.4.22-v5 appscode/stash-mongodb -n kube-system --version=3.4.22-v5 --values values.yaml
+$ helm install stash-mongodb-3.4.22-v6 appscode/stash-mongodb -n kube-system --version=3.4.22-v6 --values values.yaml
 ```
diff --git a/charts/stash-mongodb/doc.yaml b/charts/stash-mongodb/doc.yaml
@@ -10,11 +10,11 @@ repository:
   name: appscode
 chart:
   name: stash-mongodb
-  version: 3.4.22-v5
+  version: 3.4.22-v6
   values: "-- generate from values file --"
   valuesExample: "-- generate from values file --"
 prerequisites:
 - Kubernetes 1.11+
 release:
-  name: stash-mongodb-3.4.22-v5
+  name: stash-mongodb-3.4.22-v6
   namespace: kube-system
diff --git a/charts/stash-mongodb/values.yaml b/charts/stash-mongodb/values.yaml
@@ -13,7 +13,7 @@ image:
   repository: stash-mongodb
   # Tag of the image that is used to backup/restore MongoDB database.
   # This is usually same as the database version it can backup.
-  tag: 3.4.22-v5
+  tag: 3.4.22-v6
 # optional argument to send mongodump or mongorestore command
 backup:
   # Arguments to pass to `mongodump` command during backup process

diff --git a/docs/examples/backup/replicaset/backupconfiguration-replicaset.yaml b/docs/examples/backup/replicaset/backupconfiguration-replicaset.yaml
@@ -6,7 +6,7 @@ metadata:
 spec:
   schedule: "*/5 * * * *"
   task:
-    name: mongodb-backup-3.4.22-v5
+    name: mongodb-backup-3.4.22-v6
   repository:
     name: gcs-repo-replicaset
   target:

diff --git a/docs/examples/backup/replicaset/mongodb-replicaset-ssl.yaml b/docs/examples/backup/replicaset/mongodb-replicaset-ssl.yaml
@@ -4,7 +4,7 @@ metadata:
   name: sample-mgo-rs-ssl
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   replicas: 3
   replicaSet:
     name: rs0

diff --git a/docs/examples/backup/replicaset/mongodb-replicaset.yaml b/docs/examples/backup/replicaset/mongodb-replicaset.yaml
@@ -4,7 +4,7 @@ metadata:
   name: sample-mgo-rs
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   replicas: 3
   replicaSet:
     name: rs0

diff --git a/docs/examples/backup/replicaset/standalone-backup.yaml b/docs/examples/backup/replicaset/standalone-backup.yaml
@@ -33,7 +33,7 @@ metadata:
 spec:
   schedule: "*/5 * * * *"
   task:
-    name: mongodb-backup-3.4.22-v5
+    name: mongodb-backup-3.4.22-v6
   repository:
     name: gcs-repo-custom
   target:

diff --git a/docs/examples/backup/sharding/backupconfiguration-sharding.yaml b/docs/examples/backup/sharding/backupconfiguration-sharding.yaml
@@ -6,7 +6,7 @@ metadata:
 spec:
   schedule: "*/5 * * * *"
   task:
-    name: mongodb-backup-3.4.22-v5
+    name: mongodb-backup-3.4.22-v6
   repository:
     name: gcs-repo-sharding
   target:

diff --git a/docs/examples/backup/sharding/mongodb-sharding-ssl.yaml b/docs/examples/backup/sharding/mongodb-sharding-ssl.yaml
@@ -4,7 +4,7 @@ metadata:
   name: sample-mgo-sh-ssl
   namespace: demo
 spec:
-  version: 3.4.22
+  version: "3.4.22-v1"
   shardTopology:
     configServer:
       replicas: 3

diff --git a/docs/examples/backup/sharding/mongodb-sharding.yaml b/docs/examples/backup/sharding/mongodb-sharding.yaml
@@ -4,7 +4,7 @@ metadata:
   name: sample-mgo-sh
   namespace: demo
 spec:
-  version: 3.4.22
+  version: "3.4.22-v1"
   shardTopology:
     configServer:
       replicas: 3

diff --git a/docs/examples/backup/sharding/standalone-backup.yaml b/docs/examples/backup/sharding/standalone-backup.yaml
@@ -33,7 +33,7 @@ metadata:
 spec:
   schedule: "*/5 * * * *"
   task:
-    name: mongodb-backup-3.4.22-v5
+    name: mongodb-backup-3.4.22-v6
   repository:
     name: gcs-repo-custom
   target:

diff --git a/docs/examples/backup/standalone/backupconfiguration.yaml b/docs/examples/backup/standalone/backupconfiguration.yaml
@@ -6,7 +6,7 @@ metadata:
 spec:
   schedule: "*/5 * * * *"
   task:
-    name: mongodb-backup-3.4.22-v5
+    name: mongodb-backup-3.4.22-v6
   repository:
     name: gcs-repo
   target:

diff --git a/docs/examples/backup/standalone/mongodb-ssl.yaml b/docs/examples/backup/standalone/mongodb-ssl.yaml
@@ -4,7 +4,7 @@ metadata:
   name: sample-mongodb-ssl
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   storageType: Durable
   storage:
     storageClassName: "standard"

diff --git a/docs/examples/backup/standalone/mongodb.yaml b/docs/examples/backup/standalone/mongodb.yaml
@@ -4,7 +4,7 @@ metadata:
   name: sample-mongodb
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   storageType: Durable
   storage:
     storageClassName: "standard"

diff --git a/docs/examples/restore/replicaset/restored-mongodb-replicaset.yaml b/docs/examples/restore/replicaset/restored-mongodb-replicaset.yaml
@@ -4,7 +4,7 @@ metadata:
   name: restored-mgo-rs
   namespace: demo
 spec:
-  version: "4.1.13"
+  version: "3.4.22-v1"
   authSecret:
     name: sample-mgo-rs-auth
   replicas: 3

diff --git a/docs/examples/restore/replicaset/restored-standalone.yaml b/docs/examples/restore/replicaset/restored-standalone.yaml
@@ -4,7 +4,7 @@ metadata:
   name: restored-mongodb
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   storageType: Durable
   authSecret:
     name: sample-mgo-rs-auth

diff --git a/docs/examples/restore/replicaset/restoresession-replicaset.yaml b/docs/examples/restore/replicaset/restoresession-replicaset.yaml
@@ -7,7 +7,7 @@ metadata:
     app.kubernetes.io/name: mongodbs.kubedb.com
 spec:
   task:
-    name: mongodb-restore-3.4.22-v5
+    name: mongodb-restore-3.4.22-v6
   repository:
     name: gcs-repo-replicaset
   target:

diff --git a/docs/examples/restore/replicaset/restoresession-standalone.yaml b/docs/examples/restore/replicaset/restoresession-standalone.yaml
@@ -7,7 +7,7 @@ metadata:
     app.kubernetes.io/name: mongodbs.kubedb.com
 spec:
   task:
-    name: mongodb-restore-3.4.22-v5
+    name: mongodb-restore-3.4.22-v6
   repository:
     name: gcs-repo-custom
   target:

diff --git a/docs/examples/restore/sharding/restored-mongodb-sharding.yaml b/docs/examples/restore/sharding/restored-mongodb-sharding.yaml
@@ -6,7 +6,7 @@ metadata:
 spec:
   authSecret:
     name: sample-mgo-sh-auth
-  version: 4.1.13
+  version: "3.4.22-v1"
   shardTopology:
     configServer:
       replicas: 3

diff --git a/docs/examples/restore/sharding/restored-standalone.yaml b/docs/examples/restore/sharding/restored-standalone.yaml
@@ -4,7 +4,7 @@ metadata:
   name: restored-mongodb
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   storageType: Durable
   authSecret:
     name: sample-mgo-sh-auth

diff --git a/docs/examples/restore/sharding/restoresession-sharding.yaml b/docs/examples/restore/sharding/restoresession-sharding.yaml
@@ -7,7 +7,7 @@ metadata:
     app.kubernetes.io/name: mongodbs.kubedb.com
 spec:
   task:
-    name: mongodb-restore-3.4.22-v5
+    name: mongodb-restore-3.4.22-v6
   repository:
     name: gcs-repo-sharding
   target:

diff --git a/docs/examples/restore/sharding/restoresession-standalone.yaml b/docs/examples/restore/sharding/restoresession-standalone.yaml
@@ -7,7 +7,7 @@ metadata:
     app.kubernetes.io/name: mongodbs.kubedb.com
 spec:
   task:
-    name: mongodb-restore-3.4.22-v5
+    name: mongodb-restore-3.4.22-v6
   repository:
     name: gcs-repo-custom
   target:

diff --git a/docs/examples/restore/standalone/restored-mongodb.yaml b/docs/examples/restore/standalone/restored-mongodb.yaml
@@ -4,7 +4,7 @@ metadata:
   name: restored-mongodb
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   storageType: Durable
   authSecret:
     name: sample-mongodb-auth

diff --git a/docs/examples/restore/standalone/restoresession.yaml b/docs/examples/restore/standalone/restoresession.yaml
@@ -7,7 +7,7 @@ metadata:
     app.kubernetes.io/name: mongodbs.kubedb.com
 spec:
   task:
-    name: mongodb-restore-3.4.22-v5
+    name: mongodb-restore-3.4.22-v6
   repository:
     name: gcs-repo
   target:

diff --git a/docs/mongodb-replicaset.md b/docs/mongodb-replicaset.md
@@ -62,7 +62,7 @@ metadata:
   name: sample-mgo-rs
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   replicas: 3
   replicaSet:
     name: rs0
@@ -151,7 +151,7 @@ spec:
   secret:
     name: sample-mgo-rs-auth
   type: kubedb.com/mongodb
-  version: "3.4.22"
+  version: "3.4.22-v1"
 ```
 
 Stash uses the `AppBinding` crd to connect with the target database. It requires the following two fields to set in AppBinding's `Spec` section.
@@ -181,7 +181,7 @@ metadata:
   name: sample-mgo-rs-ssl
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   replicas: 3
   replicaSet:
     name: rs0
@@ -226,7 +226,7 @@ spec:
   secret:
     name: sample-mgo-rs-ssl-cert
   type: kubedb.com/mongodb
-  version: 3.4.22
+  version: "3.4.22-v1"
 ```
 
 Here, `mongo-sh-rs-cert` contains few required certificates, and one of them is `client.pem` which is required to backup/restore ssl enabled mongodb server using stash-mongodb.
@@ -469,7 +469,7 @@ metadata:
   name: restored-mgo-rs
   namespace: demo
 spec:
-  version: "4.1.13"
+  version: "3.4.22-v1"
   authSecret:
     name: sample-mgo-rs-auth
   replicas: 3
@@ -726,7 +726,7 @@ metadata:
   name: restored-mongodb
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   storageType: Durable
   authSecret:
     name: sample-mgo-rs-auth

diff --git a/docs/mongodb-sharding.md b/docs/mongodb-sharding.md
@@ -62,7 +62,7 @@ metadata:
   name: sample-mgo-sh
   namespace: demo
 spec:
-  version: 3.4.22
+  version: "3.4.22-v1"
   shardTopology:
     configServer:
       replicas: 3
@@ -165,7 +165,7 @@ spec:
   secret:
     name: sample-mgo-sh-auth
   type: kubedb.com/mongodb
-  version: 3.4.22
+  version: "3.4.22-v1"
 ```
 
 Stash uses the `AppBinding` crd to connect with the target database. It requires the following two fields to set in AppBinding's `Spec` section.
@@ -196,7 +196,7 @@ metadata:
   name: sample-mgo-sh-ssl
   namespace: demo
 spec:
-  version: 3.4.22
+  version: "3.4.22-v1"
   shardTopology:
     configServer:
       replicas: 3
@@ -252,7 +252,7 @@ spec:
   secret:
     name: sample-mgo-sh-ssl-cert
   type: kubedb.com/mongodb
-  version: 3.4.22
+  version: "3.4.22-v1"
 ```
 
 Here, `sample-mgo-sh-cert` contains few required certificates, and one of them is `client.pem` which is required to backup/restore ssl enabled mongodb server using stash-mongodb.
@@ -493,7 +493,7 @@ metadata:
 spec:
   authSecret:
     name: sample-mgo-sh-auth
-  version: 4.1.13
+  version: "3.4.22-v1"
   shardTopology:
     configServer:
       replicas: 3
@@ -762,7 +762,7 @@ metadata:
   name: restored-mongodb
   namespace: demo
 spec:
-  version: "3.4.22"
+  version: "3.4.22-v1"
   storageType: Durable
   authSecret:
     name: sample-mgo-sh-auth