Bump milvus version to v2.2.7 (#440)

Signed-off-by: Edward Zeng <jie.zeng@zilliz.com>

Author: LoveEachDay

charts/milvus/Chart.yaml

@@ -1,9 +1,9 @@
 apiVersion: v1
 name: milvus
-appVersion: "2.2.6"
+appVersion: "2.2.7"
 kubeVersion: "^1.10.0-0"
 description: Milvus is an open-source vector database built to power AI applications and vector similarity search.
-version: 4.0.17
+version: 4.0.18
 keywords:
   - milvus
   - elastic

charts/milvus/README.md

@@ -152,7 +152,7 @@ The following table lists the configurable parameters of the Milvus Service and
 |-------------------------------------------|-----------------------------------------------|---------------------------------------------------------|
 | `cluster.enabled`                         | Enable or disable Milvus Cluster mode         | `true`                                                 |
 | `image.all.repository`                    | Image repository                              | `milvusdb/milvus`                                       |
-| `image.all.tag`                           | Image tag                                     | `v2.2.1`                           |
+| `image.all.tag`                           | Image tag                                     | `v2.2.7`                           |
 | `image.all.pullPolicy`                    | Image pull policy                             | `IfNotPresent`                                          |
 | `image.all.pullSecrets`                   | Image pull secrets                            | `{}`                                                    |
 | `image.tools.repository`                  | Config image repository                       | `milvusdb/milvus-config-tool`                                       |

charts/milvus/values.yaml

@@ -5,7 +5,7 @@ cluster:
 image:
   all:
     repository: milvusdb/milvus
-    tag: v2.2.6
+    tag: v2.2.7
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.
     ## Secrets must be manually created in the namespace.

charts/minio/README.md

@@ -63,7 +63,7 @@ $ helm install --set accessKey=myaccesskey,secretKey=mysecretkey --generate-name
 
 ### Updating MinIO configuration via Helm
 
-[ConfigMap](https://kubernetes.io/docs/user-guide/configmap/) allows injecting containers with configuration data even while a Helm release is deployed.
+[ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap) allows injecting containers with configuration data even while a Helm release is deployed.
 
 To update your MinIO server configuration while it is deployed in a release, you need to
 
@@ -290,7 +290,7 @@ NAS Gateway
 
 ### Prerequisites
 
-MinIO in NAS gateway mode can be used to create multiple MinIO instances backed by single PV in `ReadWriteMany` mode. Currently few [Kubernetes volume plugins](https://kubernetes.io/docs/user-guide/persistent-volumes/#access-modes) support `ReadWriteMany` mode. To deploy MinIO NAS gateway with Helm chart you'll need to have a Persistent Volume running with one of the supported volume plugins. [This document](https://kubernetes.io/docs/user-guide/volumes/#nfs)
+MinIO in NAS gateway mode can be used to create multiple MinIO instances backed by single PV in `ReadWriteMany` mode. Currently few [Kubernetes volume plugins](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) support `ReadWriteMany` mode. To deploy MinIO NAS gateway with Helm chart you'll need to have a Persistent Volume running with one of the supported volume plugins. [This document](https://kubernetes.io/docs/concepts/storage/volumes/#nfs)
 outlines steps to create a NFS PV in Kubernetes cluster.
 
 ### Provision NAS Gateway MinIO instances