From bd0203e6a601a102b1a7e07dbef3bef07e6b0db7 Mon Sep 17 00:00:00 2001 From: Alex Giurgiu Date: Tue, 11 Jun 2024 14:58:37 +0300 Subject: [PATCH] added readme entry for the new value field --- charts/milvus/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/charts/milvus/README.md b/charts/milvus/README.md index e32970e..e14ee22 100644 --- a/charts/milvus/README.md +++ b/charts/milvus/README.md @@ -214,7 +214,7 @@ In case you want to use a different `secretName` or mount path inside pod, modif ## Milvus with External Object Storage -As of https://github.com/minio/minio/releases/tag/RELEASE.2022-10-29T06-21-33Z, the MinIO Gateway and the related filesystem mode code have been removed. It is now recommended to utilize the `externalS3` configuration for integrating with various object storage services. Notably, Milvus now provides support for popular object storage platforms such as AWS S3, GCP GCS, Azure Blob, Aliyun OSS and Tencent COS. +As of https://github.com/minio/minio/releases/tag/RELEASE.2022-10-29T06-21-33Z, the MinIO Gateway and the related filesystem mode code have been removed. It is now recommended to utilize the `externalS3` configuration for integrating with various object storage services. Notably, Milvus now provides support for popular object storage platforms such as AWS S3, GCP GCS, Azure Blob, Aliyun OSS and Tencent COS. The recommended configuration option for `externalS3.cloudProvider` includes the following choices: `aws`, `gcp`, `azure`, `aliyun`, and `tencent`. Here's an example to use AWS S3 for Milvus object storage: @@ -266,6 +266,7 @@ The following table lists the configurable parameters of the Milvus Service and | `image.tools.repository` | Config image repository | `milvusdb/milvus-config-tool` | | `image.tools.tag` | Config image tag | `v0.1.2` | | `image.tools.pullPolicy` | Config image pull policy | `IfNotPresent` | +| `customConfigMap` | User specified ConfigMap for configuration | | `extraConfigFiles` | Extra config to override default milvus.yaml | `user.yaml:` | | `service.type` | Service type | `ClusterIP` | | `service.port` | Port where service is exposed | `19530` |