Constraints

• If an SFS file system is in use, do not modify the VPC configuration associated with the SFS file system. Otherwise, the containers in CCI will not be able to access the SFS file system.
• If an SFS file system is in use, do not adjust its capacity. Otherwise, data loss will occur.
• Exercise caution when deleting an SFS file system. After you delete an SFS file system, containers in CCI will become unavailable.

Importing SFS File Systems

CCI allows you to import existing SFS file systems.

1. Log in to the CCI console. In the navigation pane, choose Storage > SFS.
   • If you have created SFS file systems on the SFS console, go to 2.
   • If you have not created any SFS file system, go to 3.

2. Click Import. On the Import SFS File System page, select one or more file systems that you want to import and click Import.
3. Click Create SFS Volume, set parameters, and click Submit.

   

   • PVC Name: Enter the PVC name.
   • Namespace: Select the namespace to which the PVC belongs.
   • Type: Specify the file system type. Currently, only NFS is supported.
   • Total Capacity (GB): Select the required capacity. If this volume has enabled auto capacity expansion, it can be automatically scaled without capacity limit.
   • Access Mode: Specify the mode to access to the SFS volume. Currently, only ReadWriteMany is supported. To be specific, the SFS volume can be read by and written to multiple nodes.
   • Encryption: KMS Encryption is deselected by default. If you select KMS Encryption, set the following parameters:
     

     Currently, the encryption function is not available in region CN East-Shanghai1.

     • Agency Name: Agencies can be used to assign permissions to trusted accounts or cloud services for a specific period of time. If no agency is created, click Create Agency. The agency name EVSAccessKMS indicates that EVS is granted the permission to access KMS and can obtain KMS keys to encrypt and decrypt EVS disks.
     • Key Name: A secret is a type of resource that holds user-defined, sensitive data, such as authentication and key information. Secrets can be loaded into containerized applications. For details on how to create a secret, see Creating a CMK.
     • Key ID: generated by default.

4. Specify the mount option for the SFS volume to ensure real-time data access. If you mount an SFS volume to more than one pod, there will be a delay in pod metadata access due to local caching in pods.

   You can set mount options for specific SFS volumes. Currently, only the noac mount option is supported. You can use this option to disable local file and directory caching, and allow pods to access data from the SFS volume in real time.

   

   • The mount option is valid only for SFS volumes created in the current namespace.
   • Currently, the mount option configuration is not available in region CN East-Shanghai1.
   Figure 1 Setting the mount option for an SFS volume
   

Using SFS Volumes

After selecting a container image in Deployments, Creating a Job, or Creating a Cron Job, expand Advanced Settings > Storage, click the SFS Volumes tab, and click Add SFS Volume.

Figure 2 Configuring SFS volume parameters

subPath is a sub-directory in the root path of the SFS file system. If such a sub-directory does not exist, it is automatically created in the SFS file system. Note that subPath must be a relative path.

You can select automatically created or existing volumes. Before you use existing volumes, ensure that the corresponding file systems have been imported. For details, see Importing SFS File Systems.

• Do not mount SFS volumes to a system directory, such as / or /var/run. Otherwise, the container will become abnormal. You are advised to mount SFS volumes to an empty directory. If the directory is not empty, ensure that there are no files affecting container startup in the directory. Otherwise, such files will be replaced, and will result in a failure in starting the container and creating the workload.
• If you intend to mount SFS volumes to a high-risk directory, you are advised to use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may get damaged.

Creating SFS Volumes Using kubectl

For details, see Using Persistent Storage.