Skip to main content


Upgrade methods vary with different JuiceFS clients.

Mount point

The JuiceFS client only has one binary file. So to upgrade the new version, you only need to replace the old one with the new one.

  • Use pre-compiled client: Refer to Install the pre-compiled client for details.
  • Manually compile client: You can pull the latest source code and recompile it to overwrite the old version of the client. Please refer to "Installation" for details.

For the file system that has been mounted using the old version of JuiceFS client, you need to unmount file system, and then re-mount it with the new version of JuiceFS client.

When unmounting the file system, make sure that no application is accessing it. Otherwise the unmount will fail. Do not forcibly unmount the file system, as it may cause the application unable to continue to access it as expected.

Kubernetes CSI Driver

Please refer to official documentation to learn how to upgrade JuiceFS CSI Driver.

S3 Gateway

Like mount point, upgrading S3 Gateway is to replace the old version with the new version.

If it is deployed through Kubernetes, you need to upgrade according to the specific deployment method, which is described in detail below.

Upgrade via kubectl

Download and modify the juicedata/juicefs-csi-driver image tag in S3 Gateway deploy YAML to the version you want to upgrade (see here for a detailed description of all versions), and then run the following command:

kubectl apply -f ./juicefs-s3-gateway.yaml

Upgrade via Helm

Please run the following commands in sequence to upgrade the S3 Gateway:

helm repo update
helm upgrade juicefs-s3-gateway juicefs-s3-gateway/juicefs-s3-gateway -n kube-system -f ./values.yaml

Hadoop Java SDK

Please refer to Install and compile the client to learn how to install the new version of the Hadoop Java SDK, and then follow steps in Deploy the client to redeploy the new version of the client to complete the upgrade.


Some components must be restarted to use the new version of the Hadoop Java SDK. Please refer to the "Restart Services" for details.