From b31cafbe48de8a052cc0d7ea862d1141f42909bd Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Sun, 24 Jan 2021 19:06:30 -0800 Subject: [PATCH] adjust for outsideContainerClusterMode --- FUSE-Mount.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/FUSE-Mount.md b/FUSE-Mount.md index b24c16b..76eb789 100644 --- a/FUSE-Mount.md +++ b/FUSE-Mount.md @@ -34,8 +34,8 @@ However, if the SeaweedFS cluster is started by Kubernetes or docker-compose and the volume servers only knows its own IP addresses inside the cluster, `weed mount` is not able to access the volume servers from outside of the cluster. -`weed mount -outsideContainerClusterMode` option can help here. It assumes all volume server containers are accessible -through the `publicUrl` address when starting with `weed volume -publicUrl=xxx`. +`weed mount -outsideContainerClusterMode` option can help here. It will proxy the requests to volume servers via filer. +So only filer needs to be exposed. #### Multiple mounts with multiple Filers of a SeaweedFS cluster