This commit is contained in:
JohnHuang 2024-06-11 23:16:40 -07:00 committed by GitHub
commit 656a61fbd4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 4 additions and 16 deletions

View File

@ -491,16 +491,10 @@ Take MinIO as an example: Modify the following configurations in `values.yaml`:
common:
configmap:
RESOURCE_STORAGE_TYPE: "S3"
RESOURCE_UPLOAD_PATH: "/dolphinscheduler"
FS_DEFAULT_FS: "s3a://BUCKET_NAME"
FS_S3A_ENDPOINT: "http://MINIO_IP:9000"
FS_S3A_ACCESS_KEY: "MINIO_ACCESS_KEY"
FS_S3A_SECRET_KEY: "MINIO_SECRET_KEY"
...
```
Modify `BUCKET_NAME`, `MINIO_IP`, `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` to actual environment values.
> **Note**: `MINIO_IP` can only use IP instead of the domain name, because DolphinScheduler currently doesn't support S3 path style access.
For detailed explanation of specific fields, please see: [Resource Center Configuration](../resource/configuration.md)
### How to deploy specific components separately?

View File

@ -490,16 +490,10 @@ common:
common:
configmap:
RESOURCE_STORAGE_TYPE: "S3"
RESOURCE_UPLOAD_PATH: "/dolphinscheduler"
FS_DEFAULT_FS: "s3a://BUCKET_NAME"
FS_S3A_ENDPOINT: "http://MINIO_IP:9000"
FS_S3A_ACCESS_KEY: "MINIO_ACCESS_KEY"
FS_S3A_SECRET_KEY: "MINIO_SECRET_KEY"
...
```
`BUCKET_NAME`, `MINIO_IP`, `MINIO_ACCESS_KEY``MINIO_SECRET_KEY` 需要被修改为实际值
> **注意**: `MINIO_IP` 只能使用 IP 而非域名, 因为 DolphinScheduler 尚不支持 S3 路径风格访问 (S3 path style access)
对于配置其他字段相关细节, 请参考: [资源中心配置详情](../resource/configuration.md)
### 如何单独部署特定组件?