JuiceFS CSI Driver only supports container images in the ARM64 environment at v0.11.1 and later, so please make sure you are using the correct version. Compared with the installation method in the "Introduction" document, the installation method in the ARM64 environment is slightly different. The different installation methods are introduced below.
1. Install via Helm
Please use Helm chart v0.7.1 and later to install
The main difference between the installation in the ARM64 environment is "Step 1 Prepare a YAML file", you need to add the
sidecars configuration in the YAML file, the details are as follows:
- name: juicefs-sc
For the subsequent installation steps, please follow the instructions in the "Introduction" document.
2. Install via kubectl
The main difference in installation in the ARM64 environment is "Step 2 Deploy", which requires replacing the image address of several sidecar containers. Assuming that the
k8s.yaml file has been downloaded to the local directory, the specific commands are as follows:
cat ./k8s.yaml | \
sed -e 'email@example.com/k8scsi/csi-provisioner:firstname.lastname@example.org/sig-storage/csi-provisioner:v2.0.2@' \
-e 'email@example.com/k8scsi/livenessprobe:firstname.lastname@example.org/sig-storage/livenessprobe:v2.2.0@' \
-e 'email@example.com/k8scsi/csi-node-driver-registrar:firstname.lastname@example.org/sig-storage/csi-node-driver-registrar:v2.0.1@' | \
kubectl apply -f -
For other installation steps, please follow the instructions in the "Introduction" document.