Closed elonzh closed 1 year ago
Thanks for the feedback. /assign @haorenfsa could you help on investigation
@xiaofan-luan: GitHub didn't allow me to assign the following users: could, you, help, on, investigation.
Note that only milvus-io members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
/assign @haorenfsa /unassign
Hi, @elonzh Here's my configuration works in lastest helm chart (4.0.12):
externalS3:
enabled: true
cloudProvider: "aliyun"
host: "oss-cn-shanghai-internal.aliyuncs.com"
accessKey: "..."
secretKey: "..."
useSSL: true
port: 443
bucketName: "..."
rootPath: "milvus"
make sure you have specify the port
You can also use 80
port if you prefer:
externalS3:
# ...
useSSL: false
port: 80
Sry for the mess of the externalS3 configuration, we're seeking a way to make it better #22185
/unassign
@yanliang567 this can be closed
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
Is there an existing issue for this?
Environment
Current Behavior
Milvus server complains
["QueryNode init error: "] [error="attempt #0: Please use virtual hosted style to access.]
Expected Behavior
aliyun clouldProvider works as normal
Steps To Reproduce
Milvus Log
Anything else?
No response