Mount File Storage

File storage can be mounted to:

• a cloud server;
• a dedicated server;
• a Managed Kubernetes cluster.

Mount File Storage to a Cloud Server

The mounting process depends on the operating system on the server and the file storage protocol: NFSv4 or CIFS SMBv3.

NFSv4

Linux

1. Connect to the cloud server.

2. Open the CLI.

3. Install the package for the NFS protocol:

   sudo apt install nfs-common

4. Create a folder for mounting the storage:

   sudo mkdir -p /mnt/nfs

5. Mount the file storage:

   sudo mount -vt nfs "<filestorage_ip_address>:/shares/share-<mountpoint_uuid>" /mnt/nfs

   Specify:

   • <filestorage_ip_address> — file storage IP address. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Connection block → GNU/Linux tab.

Windows

To work with file storage from Windows, we recommend using file storage with the CIFS protocol. If you need to connect storage with the NFSv4 protocol, install and use a client that supports this protocol, then mount the file storage. To mount the file storage, refer to the documentation of your chosen client.

File storage only works with the NFSv4 client version. By default, Windows OS supports NFSv2 and NFSv3 client versions. For more information on NFS versions, see the NFS Overview article in the Microsoft documentation.

CIFS SMBv3

Linux

1. Connect to the cloud server.

2. Install the package for the CIFS protocol:

   sudo apt install cifs-utils

3. Create a folder for mounting the storage:

   sudo mkdir -p /mnt/cifs

4. Mount the file storage:

   sudo mount.cifs -o guest //<filestorage_ip_address>/share-<mountpoint_uuid> /mnt/cifs

   Specify:

   • <filestorage_ip_address> — file storage IP address. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Connection block → GNU/Linux tab.

Windows

1. Connect to the cloud server.

2. Open the CLI.

3. Mount the file storage:

   net use X: \\\\<filestorage_ip_address>\share-<mountpoint_uuid>

   Specify:

   • <filestorage_ip_address> — file storage IP address. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Connection block → Windows tab.

Mount File Storage to a Dedicated Server

NFSv4

Linux

1. Connect to a dedicated server.

2. Open the CLI.

3. Install the package for working with the NFS protocol:

   sudo apt install nfs-common

4. Create a folder for mounting the storage:

   sudo mkdir -p /mnt/nfs

5. Mount the file storage:

   sudo mount -vt nfs "<filestorage_ip_address>:/shares/share-<mountpoint_uuid>" /mnt/nfs

   Specify:

   • <filestorage_ip_address> — IP address of the file storage. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Settings tab → IP;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Connection block → GNU/Linux.

Windows

To work with file storage from Windows, we recommend using file storage with the CIFS protocol. If you need to connect storage using the NFS protocol, install and use a client that supports the NFSv4 protocol.

File storage only works with an NFSv4 client. By default, the Windows OS supports NFS clients of versions NFSv2 and NFSv3. More details about NFS versions are available in the article NFS overview in the Microsoft documentation.

CIFS SMBv3

Linux

1. Connect to a dedicated server.

2. Install the package for working with the CIFS protocol:

   sudo apt install cifs-utils

3. Create a folder for mounting the storage:

   sudo mkdir -p /mnt/cifs

4. Mount the file storage:

   sudo mount.cifs -o guest //<filestorage_ip_address>/share-<mountpoint_uuid> /mnt/cifs

   Specify:

   • <filestorage_ip_address> — IP address of the file storage. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Settings tab → IP;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Connection block → GNU/Linux.

Windows

1. Connect to a dedicated server.

2. Mount the file storage:

   net use X: \\\\<filestorage_ip_address>\share-<mountpoint_uuid>

   Specify:

   • <filestorage_ip_address> — IP address of the file storage. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Settings tab → IP;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → Connection block → Windows.

Mount File Storage to a Managed Kubernetes Cluster

The mounting process depends on the file storage protocol: NFSv4 or CIFS SMBv3.

NFSv4

1. Create a PersistentVolume.

2. Create a PersistentVolumeClaim.

3. Add file storage to the container.

1. Create a PersistentVolume

1. Connect to the Managed Kubernetes cluster.

2. Create a yaml file with a manifest for the PersistentVolume object:

   apiVersion: v1
   kind: PersistentVolume
   metadata:
     name: pv_name
   spec:
     storageClassName: storageclass_name
     capacity:
       storage: <storage_size>
     accessModes:
       - ReadWriteMany
     nfs:
       path: /shares/share-<mountpoint_uuid>
       server: <filestorage_ip_address>

   Specify:

   • <storage_size> — PersistentVolume size in GB (file storage size), for example 100 Gi. The limit is from 50 GB to 50 TB;
   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → block Connection → tab GNU/Linux;
   • <filestorage_ip_address> — file storage IP address. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → tab Settings → field IP.

3. Apply the manifest:

   kubectl apply -f <persistent_volume.yaml>

   Specify <persistent_volume.yaml> — the name of the yaml file with the manifest to create the PersistentVolume.

4. Make sure the PersistentVolume object is created:

   kubectl get pv

2. Create a PersistentVolumeClaim

1. Create a yaml file with a manifest for the PersistentVolumeClaim object:

   apiVersion: v1
   kind: PersistentVolumeClaim
   metadata:
     name: pvc_name
   spec:
     storageClassName: storageclass_name
     accessModes:
       - ReadWriteMany
     resources:
       requests:
         storage: <storage_size>

   Specify <storage_size> — PersistentVolume (file storage) size in GB, for example 100 Gi. The limit is from 50 GB to 50 TB.

2. Apply the manifest:

   kubectl apply -f <persistent_volume_claim.yaml>

   Specify <persistent_volume_claim.yaml> — the name of the yaml file with the manifest to create the PersistentVolumeClaim.

3. Make sure the PersistentVolumeClaim object is created:

   kubectl get pvc

3. Add storage to the container

1. Create a yaml file with a manifest for the Deployment object:

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: filestorage_deployment_name
     labels:
       project: filestorage_deployment_name
   spec:
     replicas: 2
     selector:
       matchLabels:
         project: filestorage_project_name
     template:
       metadata:
         labels:
           project: filestorage_project_name
       spec:
         volumes:
           - name: volume_name
             persistentVolumeClaim:
               claimName: pvc_name
         containers:
           - name: container-nginx
             image: nginx:stable-alpine
             ports:
               - containerPort: 80
                 name: "http-server"
             volumeMounts:
               - name: volume_name
                 mountPath: <mount_path>

   Specify <mount_path> — the path to the folder inside the container where the file storage will be mounted.

2. Apply the manifest:

   kubectl apply -f <deployment.yaml>

   Specify <deployment.yaml> — the name of the yaml file with the manifest to create the Deployment.

CIFS SMBv3

1. Install the CSI driver for Samba.

2. Create a secret to store the username and password.

3. Create a StorageClass.

4. Create a PersistentVolumeClaim.

5. Add file storage to the container.

1. Install the CSI driver for Samba

1. Connect to the Managed Kubernetes cluster.

2. Install Helm package manager.

3. Download the CSI driver from GitHub Kubernetes CSI.

4. Install the latest version of the driver:

   helm repo add csi-driver-smb https://raw.githubusercontent.com/kubernetes-csi/csi-driver-smb/master/charts
   helm install csi-driver-smb csi-driver-smb/csi-driver-smb --namespace kube-system --version v1.4.0

5. Check that the pods are installed and running:

   kubectl --namespace=kube-system get pods --selector="app=csi-smb-controller"

2. Create a secret

File storage does not support access rights differentiation. Access via the CIFS SMBv3 protocol is granted under the guest user.

Create a secret to store the username and password (the default is guest/guest):

kubectl create secret generic smbcreds --from-literal username=guest --from-literal password=guest

3. Create a StorageClass

1. Create a yaml file with a manifest for the StorageClass object:

   apiVersion: storage.k8s.io/v1
   kind: StorageClass
   metadata:
     name: storageclass_name
   provisioner: smb.csi.k8s.io
   parameters:
     source: "//<filestorage_ip_address>/share-<mountpoint_uuid>"
     csi.storage.k8s.io/provisioner-secret-name: "smbcreds"
     csi.storage.k8s.io/provisioner-secret-namespace: "default"
     csi.storage.k8s.io/node-stage-secret-name: "smbcreds"
     csi.storage.k8s.io/node-stage-secret-namespace: "default"
   reclaimPolicy: Delete
   volumeBindingMode: Immediate
   mountOptions:
     - dir_mode=0777
     - file_mode=0777

   Specify:

   • <mountpoint_uuid> — mount point ID. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → block Connection → tab GNU/Linux;
   • <filestorage_ip_address> — file storage IP address. You can view it in the control panel: from the top menu, click Products → File Storage → storage page → tab Settings → field IP.

2. Apply the manifest:

   kubectl apply -f <storage_class.yaml>

   Specify <storage_class.yaml> — the name of the yaml file with the manifest to create the StorageClass.

3. Make sure the StorageClass object is created:

   kubectl get storageclass

4. Create a PersistentVolumeClaim

1. Create a yaml file with a manifest for the PersistentVolumeClaim object:

   apiVersion: v1
   kind: PersistentVolumeClaim
   metadata:
     name: pvc_name
     annotations:
       volume.beta.kubernetes.io/storage-class: smb
   spec:
     accessModes: ["ReadWriteMany"]
     resources:
       requests:
         storage: <storage_size>

   Specify <storage_size> — PersistentVolume (file storage) size in GB, for example 100 Gi. The limit is from 50 GB to 50 TB.

2. Apply the manifest:

   kubectl apply -f <persistent_volume_claim.yaml>

   Specify <persistent_volume_claim.yaml> — the name of the yaml file with the manifest to create the PersistentVolumeClaim.

3. Make sure the PersistentVolumeClaim object is created:

   kubectl get pvc

5. Add storage to the container

1. Create a yaml file with a manifest for the Deployment object:

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: filestorage_deployment_name
     labels:
       project: filestorage_deployment_name
   spec:
     replicas: 2
     selector:
       matchLabels:
         project: filestorage_project_name
     template:
       metadata:
         labels:
           project: filestorage_project_name
       spec:
         volumes:
           - name: volume_name
             persistentVolumeClaim:
               claimName: pvc_name
         containers:
           - name: container-nginx
             image: nginx:stable-alpine
             ports:
               - containerPort: 80
                 name: "http-server"
             volumeMounts:
               - name: volume_name
                 mountPath: <mount_path>

   Specify <mount_path> — the path to the folder inside the container where the file storage will be mounted.

2. Apply the manifest:

   kubectl apply -f <deployment.yaml>

   Specify <deployment.yaml> — the name of the yaml file with the manifest to create the Deployment.