diff --git a/content/en/docs/about-this-document/_index.md b/content/en/docs/about-this-document/_index.md index ea6d77c..2730b90 100644 --- a/content/en/docs/about-this-document/_index.md +++ b/content/en/docs/about-this-document/_index.md @@ -24,28 +24,28 @@ The symbols that may be found in this document are defined as follows. -

+

Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious injury.

-

+

Indicates a hazard with a medium level of risk which, if not avoided, could result in death or serious injury.

-

+

Indicates a hazard with a low level of risk which, if not avoided, could result in minor or moderate injury.

-

+

Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results.

NOTICE is used to address practices not related to personal injury.

-

+

Supplements the important information in the main text.

NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.

diff --git a/content/en/docs/advanced-features/configuring-alua/configuring-alua-using-helm/configuring-alua-parameters-for-a-distributed-storage-backend.md b/content/en/docs/advanced-features/configuring-alua/configuring-alua-using-helm/configuring-alua-parameters-for-a-distributed-storage-backend.md index 92678cd..a6e0926 100644 --- a/content/en/docs/advanced-features/configuring-alua/configuring-alua-using-helm/configuring-alua-parameters-for-a-distributed-storage-backend.md +++ b/content/en/docs/advanced-features/configuring-alua/configuring-alua-using-helm/configuring-alua-parameters-for-a-distributed-storage-backend.md @@ -9,7 +9,7 @@ For details about how to configure ALUA for Huawei distributed storage, see the The ALUA configuration may vary according to the OS. Visit [Huawei Technical Support](https://support.huawei.com/enterprise/en/index.html), enter **Host Connectivity Guide** in the search box, and click the search button. In the search result, select the host connectivity guide for the desired OS. Configure ALUA according to the actual situation and the description in the guide. Huawei CSI will apply the configuration items you set to the initiator of the host on Huawei storage. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >A node with a Pod provisioned does not proactively change ALUA information. The host ALUA configuration changes only after a Pod is provisioned again to the node. >In non-HyperMetro scenarios of distributed storage, you are advised to set the switchover mode to "disable ALUA" \(default value\). This is because the storage system is in active/active mode and "enables ALUA" is meaningless. Therefore, you are advised not to configure ALUA parameters for distributed storage. diff --git a/content/en/docs/advanced-features/configuring-alua/configuring-alua-using-helm/configuring-alua-parameters-for-a-huawei-enterprise-storage-backend.md b/content/en/docs/advanced-features/configuring-alua/configuring-alua-using-helm/configuring-alua-parameters-for-a-huawei-enterprise-storage-backend.md index 36ed791..d889194 100644 --- a/content/en/docs/advanced-features/configuring-alua/configuring-alua-using-helm/configuring-alua-parameters-for-a-huawei-enterprise-storage-backend.md +++ b/content/en/docs/advanced-features/configuring-alua/configuring-alua-using-helm/configuring-alua-parameters-for-a-huawei-enterprise-storage-backend.md @@ -9,7 +9,7 @@ For details about how to configure ALUA for Huawei enterprise storage, see the h The ALUA configuration may vary according to the OS. Visit [Huawei Technical Support](https://support.huawei.com/enterprise/en/index.html), enter **Host Connectivity Guide** in the search box, and click the search button. In the search result, select the host connectivity guide for the desired OS. Configure ALUA according to the actual situation and the description in the guide. Huawei CSI will apply the configuration items you set to the initiator of the host on Huawei storage. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >A node with a Pod provisioned does not proactively change ALUA information. The host ALUA configuration changes only after a Pod is provisioned again to the node. ## ALUA Parameters for OceanStor V5 and OceanStor Dorado V3 Series{#section16218353201717} @@ -102,7 +102,7 @@ parameters: [Table 2](#en-us_topic_0000001352783505_en-us_topic_0000001198982584_table7143850202411) lists the ALUA parameters supported by Huawei CSI for OceanStor and OceanStor Dorado series. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >By default, the initiator host access mode of OceanStor and OceanStor Dorado series storage is "balanced mode". Therefore, you are advised not to configure ALUA parameters for OceanStor and OceanStor Dorado series storage. **Table 2** ALUA parameters for OceanStor and OceanStor Dorado series diff --git a/content/en/docs/advanced-features/configuring-storage-topology-awareness/_index.md b/content/en/docs/advanced-features/configuring-storage-topology-awareness/_index.md index 6282991..9f6b454 100644 --- a/content/en/docs/advanced-features/configuring-storage-topology-awareness/_index.md +++ b/content/en/docs/advanced-features/configuring-storage-topology-awareness/_index.md @@ -63,7 +63,7 @@ You need to configure topology labels on worker nodes in the cluster. The method - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >- A topology label must start with **topology.kubernetes.io**. Topology label examples: > - Example 1: **topology.kubernetes.io/region=China-west** > - Example 2: **topology.kubernetes.io/zone=ChengDu** diff --git a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/_index.md b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/_index.md index d199929..6848d1b 100644 --- a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/_index.md +++ b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/_index.md @@ -41,7 +41,7 @@ The PVC change feature is implemented using CRD. Related resources are described ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >- VolumeModifyClaim resources can be created, deleted, and queried, but cannot be updated. >- VolumeModifyContent resources can only be queried and are used to display the change details of a single PVC. Do not manually create, delete, or modify the resources. >- VolumeModifyContent resources are managed by VolumeModifyClaim. Do not manually manage VolumeModifyContent resources. diff --git a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/creating-a-pvc-change/creating-a-pvc-change-resource.md b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/creating-a-pvc-change/creating-a-pvc-change-resource.md index c237841..88ebe68 100644 --- a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/creating-a-pvc-change/creating-a-pvc-change-resource.md +++ b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/creating-a-pvc-change/creating-a-pvc-change-resource.md @@ -7,7 +7,7 @@ weight: 2 This section describes how to create a PVC change resource based on a configured PVC change file. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >- Only the HyperMetro active-active \(AA\) mode is supported. >- When a common volume is changed to a HyperMetro volume, only the storage volume at the primary site can be changed. >- Do not use Huawei CSI to manage a PVC during PVC change resource creation. diff --git a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/creating-a-pvc-change/preparing-a-pvc-change-file.md b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/creating-a-pvc-change/preparing-a-pvc-change-file.md index caa2b07..e9a6426 100644 --- a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/creating-a-pvc-change/preparing-a-pvc-change-file.md +++ b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/creating-a-pvc-change/preparing-a-pvc-change-file.md @@ -108,7 +108,7 @@ The sample template of the PVC change file is **/examples/volumemodifyclaim.yam ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >- The **spec.source.kind** and **spec.source.name** parameters are used to specify the volume change scope. For example, if they are set to a StorageClass and the corresponding name respectively, all PVCs in the **Bound** state provisioned using the target StorageClass will be changed. >- After all associated PVCs are changed, Huawei CSI will replace the original StorageClass and add the **spec.parameters** parameter of the VolumeModifyClaim so that the PVCs meet the StorageClass definition. diff --git a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/deleting-a-pvc-change.md b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/deleting-a-pvc-change.md index b72fb7c..669e5dd 100644 --- a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/deleting-a-pvc-change.md +++ b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/deleting-a-pvc-change.md @@ -5,7 +5,7 @@ description: weight: 3 --- ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- If **STATUS** of a VolumeModifyClaim is **Creating**, deleting the VolumeModifyClaim resource will delete the created resource on the storage side and then remove the cluster resource. After the deletion, if you continue to use the original StorageClass for PVC management, you need to restore the associated storage backend to a non-HyperMetro storage backend. >- If **STATUS** of a VolumeModifyClaim is **Pending** or **Completed**, deleting the VolumeModifyClaim resource will only remove the cluster resource and will not delete the created resource on the storage side \(that is, there is not interaction with the storage side\). >- VolumeModifyContent resources are managed by VolumeModifyClaim. Do not manually manage VolumeModifyContent resources. diff --git a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/querying-a-pvc-change.md b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/querying-a-pvc-change.md index 0bc601e..ba2b0a1 100644 --- a/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/querying-a-pvc-change.md +++ b/content/en/docs/advanced-features/pvc-change/configuring-pvc-changes/querying-a-pvc-change.md @@ -78,7 +78,7 @@ To query a VolumeModifyClaim using kubectl, perform the following steps. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >You can use kubectl to view the **Events** information of a VolumeModifyClaim. If a VolumeModifyClaim cannot meet the creation requirements or an error occurs during the creation, the server will record the **Events** information. The following command is used as an example: >``` >kubectl describe volumemodifyclaims local-to-hypermetro @@ -150,7 +150,7 @@ A VolumeModifyContent is created using a VolumeModifyClaim and records the chang ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >You can use kubectl to view the **Events** information of a VolumeModifyContent. If a VolumeModifyContent cannot meet the creation requirements or an error occurs during the PVC change, the server will record the **Events** information. The following command is used as an example: >``` >kubectl describe volumemodifycontents myvmc-uid diff --git a/content/en/docs/advanced-features/pvc-change/enabling-the-pvc-change-feature/enabling-the-pvc-change-feature-using-helm.md b/content/en/docs/advanced-features/pvc-change/enabling-the-pvc-change-feature/enabling-the-pvc-change-feature-using-helm.md index 356f978..64aabfd 100644 --- a/content/en/docs/advanced-features/pvc-change/enabling-the-pvc-change-feature/enabling-the-pvc-change-feature-using-helm.md +++ b/content/en/docs/advanced-features/pvc-change/enabling-the-pvc-change-feature/enabling-the-pvc-change-feature-using-helm.md @@ -39,7 +39,7 @@ weight: 1 customresourcedefinition.apiextensions.k8s.io/volumemodifycontents.xuanwu.huawei.io configured ``` - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >If the command output contains **Warning: resource customresourcedefinitions/volumemodifycontents.xuanwu.huawei.io is missing the kubectl.kubernetes.io/last-applied-configuration...**, you can ignore it. This message is displayed because the **kubectl create** command instead of the **kubectl apply** command is used for installation by Helm. 4. Run the following command to obtain the original service configuration file. diff --git a/content/en/docs/appendix/configuring-custom-permissions.md b/content/en/docs/appendix/configuring-custom-permissions.md index 31223e9..b6e2666 100644 --- a/content/en/docs/appendix/configuring-custom-permissions.md +++ b/content/en/docs/appendix/configuring-custom-permissions.md @@ -12,7 +12,7 @@ For different storage resources, refer to the following configurations: - For NAS resources, configure the minimum permissions by referring to [Table 1](#table66121923174916). - For SAN resources, configure the minimum permissions by referring to [Table 2](#table51362243359). ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >For details about how to configure permissions for user-defined roles, see [OceanStor Dorado 6000, Dorado 18000 Series Product Documentation](https://support.huawei.com/hedex/hdx.do?docid=EDOC1100214756&id=EN-US_TOPIC_0000001640708705&lang=en). **Table 1** Minimum permissions for NAS resources diff --git a/content/en/docs/appendix/huawei-csi-resource-management.md b/content/en/docs/appendix/huawei-csi-resource-management.md index 70d0418..e9ca9d2 100644 --- a/content/en/docs/appendix/huawei-csi-resource-management.md +++ b/content/en/docs/appendix/huawei-csi-resource-management.md @@ -184,7 +184,7 @@ If you need to modify the resource requests and limits of a container, perform t - If the Pod name is **huawei-csi-controller**, modify the **huawei-csi-controller.yaml** file. - If the Pod name is **huawei-csi-node**, modify the **huawei-csi-node.yaml** file. - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >For details about Pod names, see [Table 1](#table4106151116363). For example, to modify the resource request of the **huawei-csi-driver** container in the Pod named **huawei-csi-node**, run the following command to edit the configuration file and find the container whose **spec.template.spec.containes.name** is **huawei-csi-driver**. Modify resource requests and limits as required. diff --git a/content/en/docs/common-operations/enabling-the-readwriteoncepod-feature-gate.md b/content/en/docs/common-operations/enabling-the-readwriteoncepod-feature-gate.md index 138debe..4f41cb4 100644 --- a/content/en/docs/common-operations/enabling-the-readwriteoncepod-feature-gate.md +++ b/content/en/docs/common-operations/enabling-the-readwriteoncepod-feature-gate.md @@ -9,7 +9,7 @@ The ReadWriteOnce access mode is the fourth access mode introduced by Kubernetes The ReadWriteOncePod access mode is an alpha feature in Kubernetes v1.22/1.23/1.24. Therefore, you need to enable the ReadWriteOncePod feature in **feature-gates** of kube-apiserver, kube-scheduler, and kubelet before using the access mode. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >Currently, the CCE or CCE Agile platform does not support the ReadWriteOncePod feature gate. ## Procedure{#en-us_topic_0000001259843616_section137882216292} @@ -28,7 +28,7 @@ The ReadWriteOncePod access mode is an alpha feature in Kubernetes v1.22/1.23/1. ... ``` - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >After the editing is complete, Kubernetes will automatically apply the updates. 2. Enable the ReadWriteOncePod feature gate for kube-scheduler. @@ -45,12 +45,12 @@ The ReadWriteOncePod access mode is an alpha feature in Kubernetes v1.22/1.23/1. ... ``` - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >After the editing is complete, Kubernetes will automatically apply the updates. 3. Enable the ReadWriteOncePod feature gate for kubelet. - >![](/public_sys-resources/en/icon-notice.gif) + >![](/css-docs/public_sys-resources/en/icon-notice.gif) >The dynamic Kubelet configuration function is not used since v1.22 and deleted in v1.24. Therefore, you need to perform the following operations on kubelet on each worker node in the cluster. 1. Use a remote access tool, such as PuTTY, to log in to any worker node in the Kubernetes cluster through the management IP address. @@ -63,7 +63,7 @@ The ReadWriteOncePod access mode is an alpha feature in Kubernetes v1.22/1.23/1. ... ``` - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >The default path of the kubelet configuration file is **/var/lib/kubelet/config.yaml**. Enter the path based on site requirements. 3. After the configuration is complete, run the **systemctl restart kubelet** command to restart kubelet. diff --git a/content/en/docs/compatibility-and-features/kubernetes-and-os-compatibility.md b/content/en/docs/compatibility-and-features/kubernetes-and-os-compatibility.md index c8f8273..9b00c54 100644 --- a/content/en/docs/compatibility-and-features/kubernetes-and-os-compatibility.md +++ b/content/en/docs/compatibility-and-features/kubernetes-and-os-compatibility.md @@ -44,7 +44,7 @@ Huawei CSI plug-in supports the following container management platforms. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- The connection between Huawei CSI and Tanzu Kubernetes supports only the centralized storage NAS scenario. For the related FAQ, see [Common Problems and Solutions for Interconnecting with the Tanzu Kubernetes Cluster](/docs/troubleshooting/common-problems-and-solutions-for-interconnecting-with-the-tanzu-kubernetes-cluster). >- The connection between Huawei CSI and CCE or CCE Agile supports only centralized storage. @@ -227,7 +227,7 @@ Note 2: Only Kylin ARM V10 SP3 supports UltraPath 31.3.0. Note 3: Anolis OS supports only OceanStor Pacific storage. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >For DM-Multipath 0.7, some virtual devices may not be displayed in the command output after the **multipathd show maps** command is executed. Therefore, you are advised to use version 0.8 or later. >You can query the DM-Multipath version in either of the following ways: >- If the rpm package is used, run the **rpm -qa | grep multipath** or **rpm -qa | grep device-mapper** command. diff --git a/content/en/docs/installation-and-deployment/installation-preparations/checking-the-host-multipathing-configuration.md b/content/en/docs/installation-and-deployment/installation-preparations/checking-the-host-multipathing-configuration.md index 5260548..f00c28a 100644 --- a/content/en/docs/installation-and-deployment/installation-preparations/checking-the-host-multipathing-configuration.md +++ b/content/en/docs/installation-and-deployment/installation-preparations/checking-the-host-multipathing-configuration.md @@ -9,7 +9,7 @@ If you plan to use the FC/iSCSI/NVMe over RoCE/NVMe over FC protocol to access H For details about the OSs and multipathing software supported by Huawei CSI, see [Table 2](/docs/compatibility-and-features/kubernetes-and-os-compatibility#table133422378818). ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >- If you want to use the FC/iSCSI protocol to connect to Huawei storage, you are advised to use native DM-Multipath provided by the OS. >- If you want to use the NVMe over RoCE/NVMe over FC protocol to connect to Huawei storage, you are advised to use Huawei-developed UltraPath-NVMe. >- If you want to use the SCSI protocol to connect to Huawei storage, disable DM-Multipath provided by the OS. @@ -37,6 +37,6 @@ Multipathing software has been correctly installed on a host. If the configuration item does not exist, add it to the beginning of the **/etc/multipath.conf** file. - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >For details about the functions of the **user\_friendly\_names** and **find\_multipaths** parameters, see [dm\_multipath/config\_file\_defaults](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/dm_multipath/config_file_defaults). diff --git a/content/en/docs/installation-and-deployment/installation-preparations/checking-the-images-on-which-csi-depends.md b/content/en/docs/installation-and-deployment/installation-preparations/checking-the-images-on-which-csi-depends.md index 8b1d115..2a303a6 100644 --- a/content/en/docs/installation-and-deployment/installation-preparations/checking-the-images-on-which-csi-depends.md +++ b/content/en/docs/installation-and-deployment/installation-preparations/checking-the-images-on-which-csi-depends.md @@ -140,6 +140,6 @@ For details about the functions and details of each image, see the following tab ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >If the cluster is not connected to the Internet, manually download the container images and upload them to the cluster. For details, see [Downloading a Container Image](/docs/common-operations/downloading-a-container-image). diff --git a/content/en/docs/installation-and-deployment/installation-preparations/checking-user-configurations-on-huawei-storage.md b/content/en/docs/installation-and-deployment/installation-preparations/checking-user-configurations-on-huawei-storage.md index 3b9a1e4..3199a64 100644 --- a/content/en/docs/installation-and-deployment/installation-preparations/checking-user-configurations-on-huawei-storage.md +++ b/content/en/docs/installation-and-deployment/installation-preparations/checking-user-configurations-on-huawei-storage.md @@ -100,6 +100,6 @@ After Huawei storage is connected to the container platform, Huawei CSI needs to - Note 1: If a user-defined role is used, you need to configure permissions for the role. For details about how to configure the minimum permissions, see [Configuring Custom Permissions](/docs/appendix/configuring-custom-permissions). ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >You are advised not to use the users of the super administrator role. diff --git a/content/en/docs/installation-and-deployment/installation-preparations/checking-volume-snapshot-dependent-components.md b/content/en/docs/installation-and-deployment/installation-preparations/checking-volume-snapshot-dependent-components.md index f4b69e3..fb288dc 100644 --- a/content/en/docs/installation-and-deployment/installation-preparations/checking-volume-snapshot-dependent-components.md +++ b/content/en/docs/installation-and-deployment/installation-preparations/checking-volume-snapshot-dependent-components.md @@ -7,7 +7,7 @@ weight: 4 This section describes how to check the volume snapshot-dependent components in the cluster. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >Kubernetes earlier than v1.17.0 does not support the snapshot function. If the snapshot CRD is deployed, the cluster may be faulty. Therefore, if Huawei CSI is deployed on Kubernetes earlier than v1.17.0, perform the check according to [Kubernetes Earlier Than v1.17.0](#section6894165917369). ## Kubernetes Earlier Than v1.17.0{#section6894165917369} diff --git a/content/en/docs/installation-and-deployment/installation-preparations/downloading-the-huawei-csi-software-package.md b/content/en/docs/installation-and-deployment/installation-preparations/downloading-the-huawei-csi-software-package.md index 0238792..077df49 100644 --- a/content/en/docs/installation-and-deployment/installation-preparations/downloading-the-huawei-csi-software-package.md +++ b/content/en/docs/installation-and-deployment/installation-preparations/downloading-the-huawei-csi-software-package.md @@ -10,7 +10,7 @@ This section describes how to download the software package and the component st 1. Open a browser and enter [https://github.com/Huawei/eSDK\_K8S\_Plugin/releases](https://github.com/Huawei/eSDK_K8S_Plugin/releases) in the address box. 2. Download the software package of the 4.5.0 version based on the CPU architecture. - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >Software package naming rule: Plug-in name \(**eSDK\_Huawei\_Storage\_Kubernetes\_CSI\_Plugin**\) + Version number + CPU architecture 3. Decompress the downloaded software package. The following table shows the component structure of the software package. diff --git a/content/en/docs/installation-and-deployment/installation-preparations/uploading-a-huawei-csi-image.md b/content/en/docs/installation-and-deployment/installation-preparations/uploading-a-huawei-csi-image.md index cd2e438..9324e63 100644 --- a/content/en/docs/installation-and-deployment/installation-preparations/uploading-a-huawei-csi-image.md +++ b/content/en/docs/installation-and-deployment/installation-preparations/uploading-a-huawei-csi-image.md @@ -45,7 +45,7 @@ A Linux host with Docker installed is available, and the host can access the ima docker push repo.huawei.com/huawei-csi:4.5.0 ``` ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- You can also use containerd to import and upload the images. >- For details about how to import and upload images to the CCE or CCE Agile platform, see the user manual of the platform. @@ -83,6 +83,6 @@ If the image has been uploaded to the image repository, skip this section. podman load -i .tar ``` - >![](/public_sys-resources/en/icon-notice.gif) + >![](/css-docs/public_sys-resources/en/icon-notice.gif) >If another container engine is installed on the node, use the image import command for the corresponding container engine. diff --git a/content/en/docs/installation-and-deployment/installing-huawei-csi/_index.md b/content/en/docs/installation-and-deployment/installing-huawei-csi/_index.md index cecc64b..69e4c41 100644 --- a/content/en/docs/installation-and-deployment/installing-huawei-csi/_index.md +++ b/content/en/docs/installation-and-deployment/installing-huawei-csi/_index.md @@ -7,7 +7,7 @@ weight: 2 This section describes how to install Huawei CSI. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >In the current version, resource requests and limits are added to Huawei CSI. For details, see [Huawei CSI Resource Management](/docs/appendix/huawei-csi-resource-management). ## Prerequisites{#en-us_topic_0000001324610777_section19453102010152} diff --git a/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/_index.md b/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/_index.md index 4e19579..b9d6a45 100644 --- a/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/_index.md +++ b/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/_index.md @@ -9,7 +9,7 @@ weight: 1 This section describes how to install Huawei CSI using Helm 3. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- Huawei CSI can be installed as the root user or a non-root user. When installing Huawei CSI as a non-root user, ensure that the current user can access the API Server of the Kubernetes cluster. For details about how to configure access to the Kubernetes cluster as a non-root user, see [Configuring Access to the Kubernetes Cluster as a Non-root User](/docs/common-operations/configuring-access-to-the-kubernetes-cluster-as-a-non-root-user). >- Huawei CSI must be run as the root user. diff --git a/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/installing-huawei-csi-on-the-cce-or-cce-agile-platform.md b/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/installing-huawei-csi-on-the-cce-or-cce-agile-platform.md index ffc8676..b40da3c 100644 --- a/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/installing-huawei-csi-on-the-cce-or-cce-agile-platform.md +++ b/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/installing-huawei-csi-on-the-cce-or-cce-agile-platform.md @@ -59,13 +59,13 @@ The CCE or CCE Agile platform cannot directly install Huawei CSI using Helm. You 3. Export the Helm installation package. For details, see [Creating a Helm Installation Package](#section2032812215509). 4. On the home page, choose **Charts** \> **My Charts** \> **Upload Chart**. The **Upload Chart** dialog box is displayed. Import the exported Helm installation package to the CCE Agile platform. - ![](/figures/上传模板-en.png) + ![](/css-docs/figures/上传模板-en.png) 5. After the installation package is uploaded, choose **Charts** \> **My Charts**. On the **My Charts** page that is displayed, choose **Install** \> **Submit**. The chart release name can be customized. - ![](/figures/安装csi-en.png) + ![](/css-docs/figures/安装csi-en.png) 6. On the home page, choose **Charts** \> **Releases** and select the project specified during installation \(for example, **default** in the following figure\). After the installation is successful, **Installed** is displayed in the **Status** column. - ![](/figures/安装结果-en.png) + ![](/css-docs/figures/安装结果-en.png) diff --git a/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/parameters-in-the-values-yaml-file-of-helm.md b/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/parameters-in-the-values-yaml-file-of-helm.md index b358193..81b5d17 100644 --- a/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/parameters-in-the-values-yaml-file-of-helm.md +++ b/content/en/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/parameters-in-the-values-yaml-file-of-helm.md @@ -128,7 +128,7 @@ The images parameters in the **values.yaml** file are used to configure the co ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- For details about the values of **huaweiCSIService**, **storageBackendSidecar**, **storageBackendController**, and **huaweiCSIExtender**, see [Uploading a Huawei CSI Image](/docs/installation-and-deployment/installation-preparations/uploading-a-huawei-csi-image). Use the name and version of the finally generated image. >- For details about other sidecar image parameters, see [Checking the Images on Which CSI Depends](/docs/installation-and-deployment/installation-preparations/checking-the-images-on-which-csi-depends). Use the name and version of the finally uploaded image. @@ -291,7 +291,7 @@ The controller parameters are used to configure the huawei-csi-controller compon ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >If **controller.snapshot.enabled** is set to **true**, you need to install the volume snapshot CRD resource in the **helm/crd/snapshot-crds** directory. ## node Parameters{#section374014171581} @@ -631,7 +631,7 @@ The csiDriver parameters include the basic configurations for running Huawei CSI ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >If Huawei CSI has been deployed in your container environment, ensure that the value of **csiDriver.driverName** is the same as that configured during previous deployment. Otherwise, existing volumes or snapshots provisioned by Huawei CSI in the system cannot be managed by the newly deployed Huawei CSI. ## Other Parameters{#section11500468593} @@ -771,7 +771,7 @@ Other parameters include some features of the CSI plug-in or the policies for ob ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >Ensure that the namespace entered in **kubernetes.namespace** exists on Kubernetes. If the namespace does not exist, run the following command to create it. In this example, the namespace for running Huawei CSI is **huawei-csi**. >``` >kubectl create namespace huawei-csi diff --git a/content/en/docs/installation-and-deployment/installing-huawei-csi/manually-installing-huawei-csi.md b/content/en/docs/installation-and-deployment/installing-huawei-csi/manually-installing-huawei-csi.md index 03204c0..d086eb9 100644 --- a/content/en/docs/installation-and-deployment/installing-huawei-csi/manually-installing-huawei-csi.md +++ b/content/en/docs/installation-and-deployment/installing-huawei-csi/manually-installing-huawei-csi.md @@ -7,7 +7,7 @@ weight: 2 This section describes how to manually install Huawei CSI. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >Currently, only the Kubernetes platform supports manual installation of Huawei CSI. ## Procedure{#section113761618183018} @@ -46,7 +46,7 @@ This section describes how to manually install Huawei CSI. 8. Run the following command to install the huawei-csi-controller service. - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >If the Kubernetes version is earlier than v1.17, modify the _./deploy/huawei-csi-controller.yaml_ file as follows: >- If the Kubernetes version is earlier than v1.17, the snapshot feature is not supported. In this case, delete the snapshot-related container configurations items **csi-snapshotter** and **snapshot-controller**. >- If the Kubernetes version is earlier than v1.17, the csi-provisioner sidecar image provided by the Kubernetes community does not support the **--leader-election** parameter. Therefore, the **leader-election** parameter of the csi-provisioner container is deleted and only single-copy deployment is supported. @@ -78,7 +78,7 @@ This section describes how to manually install Huawei CSI. huawei-csi-node-xrntc 3/3 Running 0 13m ``` ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >In the multi-copy controller deployment scenario, you can modify the **spec.replica** field of the Deployment resource in the _./deploy/huawei-csi-controller.yaml_ file to specify the number of copies. After the modification, run the following command for the modification to take effect. >``` >kubectl apply -f ./deploy/huawei-csi-controller.yaml diff --git a/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/_index.md b/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/_index.md index cc47aac..b4c7374 100644 --- a/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/_index.md +++ b/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/_index.md @@ -7,7 +7,7 @@ weight: 3 This chapter describes how to uninstall Huawei CSI. The uninstallation method varies according to the installation mode. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >If you do not uninstall Huawei CSI for the purpose of an upgrade, ensure that all resources \(such as PV, PVC, snapshot, and storage backend resources\) provisioned by Huawei CSI have been cleared on your container platform before uninstalling Huawei CSI. Otherwise, once you uninstall Huawei CSI, these resources cannot be automatically scheduled, managed, or cleared. diff --git a/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/manually-uninstalling-huawei-csi.md b/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/manually-uninstalling-huawei-csi.md index bfbb3d1..ee0aded 100644 --- a/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/manually-uninstalling-huawei-csi.md +++ b/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/manually-uninstalling-huawei-csi.md @@ -7,7 +7,7 @@ weight: 2 This section describes how to manually uninstall Huawei CSI. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >If you do not uninstall Huawei CSI for the purpose of an upgrade, ensure that all resources \(such as PV, PVC, snapshot, and storage backend resources\) provisioned by Huawei CSI have been cleared on your container platform before uninstalling Huawei CSI. Otherwise, once you uninstall Huawei CSI, these resources cannot be automatically scheduled, managed, or cleared. ## Uninstalling the huawei-csi-node Service{#section1012817231386} diff --git a/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-csi-dependent-component-services.md b/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-csi-dependent-component-services.md index 8f934af..79f0904 100644 --- a/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-csi-dependent-component-services.md +++ b/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-csi-dependent-component-services.md @@ -62,7 +62,7 @@ The webhook resource named **storage-backend-controller.xuanwu.huawei.io** is ## Uninstalling the Snapshot-Dependent Component Service{#section48371491319} ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- Do not uninstall the snapshot-dependent component service when snapshots exist. Otherwise, Kubernetes will automatically delete all user snapshots and they cannot be restored. Exercise caution when performing this operation. For details, see [Delete a CustomResourceDefinition](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#delete-a-customresourcedefinition). >- Do not uninstall the snapshot-dependent component service during the CSI upgrade. diff --git a/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-huawei-csi-on-cce-or-cce-agile.md b/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-huawei-csi-on-cce-or-cce-agile.md index 762ca80..bdc0716 100644 --- a/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-huawei-csi-on-cce-or-cce-agile.md +++ b/content/en/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-huawei-csi-on-cce-or-cce-agile.md @@ -13,7 +13,7 @@ This section describes how to uninstall Huawei CSI on the CCE or CCE Agile platf 2. On the home page, choose **Charts** \> **Releases**. The **Releases** page is displayed. 3. Select a Huawei CSI release and click **Uninstall**. In the displayed dialog box, click **OK**. - ![](/figures/卸载-en.png) + ![](/css-docs/figures/卸载-en.png) 4. Uninstall the huawei-csi-host-info object. For details, see [Uninstalling the huawei-csi-host-info Object](/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-csi-dependent-component-services#section870813403017). 5. Uninstall the webhook resource. For details, see [Uninstalling a Webhook Resource](/docs/installation-and-deployment/uninstalling-huawei-csi/uninstalling-huawei-csi-using-helm/uninstalling-csi-dependent-component-services#section871155813014). diff --git a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/_index.md b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/_index.md index de63115..5c74b94 100644 --- a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/_index.md +++ b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/_index.md @@ -7,7 +7,7 @@ weight: 4 This section describes how to upgrade or roll back Huawei CSI. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >In the current version, resource requests and limits are added to Huawei CSI. For details, see [Huawei CSI Resource Management](/docs/appendix/huawei-csi-resource-management). diff --git a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/manual-upgrade-rollback/rolling-back-huawei-csi-1.md b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/manual-upgrade-rollback/rolling-back-huawei-csi-1.md index 85abc79..ab46f66 100644 --- a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/manual-upgrade-rollback/rolling-back-huawei-csi-1.md +++ b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/manual-upgrade-rollback/rolling-back-huawei-csi-1.md @@ -7,7 +7,7 @@ weight: 2 Uninstall CSI by referring to [Manually Uninstalling Huawei CSI](/docs/installation-and-deployment/uninstalling-huawei-csi/manually-uninstalling-huawei-csi), and then download and install CSI of the source version. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- During the upgrade or rollback, the existing resources such as PVCs, snapshots, and Pods will run properly and will not affect your service access. >- During the upgrade or rollback, you cannot use Huawei CSI to create new resources or mount or unmount an existing PVC. >- During the upgrade or rollback, do not uninstall the snapshot-dependent component service. diff --git a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/manual-upgrade-rollback/upgrading-huawei-csi-0.md b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/manual-upgrade-rollback/upgrading-huawei-csi-0.md index c50e441..e47426a 100644 --- a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/manual-upgrade-rollback/upgrading-huawei-csi-0.md +++ b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/manual-upgrade-rollback/upgrading-huawei-csi-0.md @@ -9,7 +9,7 @@ This section describes how to manually upgrade Huawei CSI. During the upgrade or rollback, the existing resources such as PVCs, snapshots, and Pods will run properly and will not affect your service access. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- Some CSI 2._x_ versions are unavailable now. If the upgrade fails, CSI may fail to be rolled back to a version which is unavailable now. >- During the upgrade or rollback, you cannot use Huawei CSI to create new resources or mount or unmount an existing PVC. >- During the upgrade or rollback, do not uninstall the snapshot-dependent component service. diff --git a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/rolling-back-huawei-csi/rolling-back-huawei-csi-on-cce-or-cce-agile.md b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/rolling-back-huawei-csi/rolling-back-huawei-csi-on-cce-or-cce-agile.md index 3e973df..d3a1cc6 100644 --- a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/rolling-back-huawei-csi/rolling-back-huawei-csi-on-cce-or-cce-agile.md +++ b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/rolling-back-huawei-csi/rolling-back-huawei-csi-on-cce-or-cce-agile.md @@ -5,7 +5,7 @@ description: weight: 2 --- ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- During the upgrade or rollback, the existing resources such as PVCs, snapshots, and Pods will run properly and will not affect your service access. >- During the upgrade or rollback, you cannot use Huawei CSI to create new resources or mount or unmount an existing PVC. >- During the upgrade or rollback, do not uninstall the snapshot-dependent component service. diff --git a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/_index.md b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/_index.md index da8c9ce..6930ff4 100644 --- a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/_index.md +++ b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/_index.md @@ -9,7 +9,7 @@ This section describes how to upgrade Huawei CSI. During the upgrade or rollback, the existing resources such as PVCs, snapshots, and Pods will run properly and will not affect your service access. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- Some CSI 2._x_ versions are unavailable now. If the upgrade fails, CSI may fail to be rolled back to a version which is unavailable now. >- After an upgrade from 2._x_, 3._x_, or 4._x_ to 4.5.0, a Pod that has been provisioned in the source version may fail to be mounted again. For details, see [Upgrading from 2.x or 3.x to 4.x](/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/upgrading-from-2-x-or-3-x-to-4-x). >- During the upgrade or rollback, you cannot use Huawei CSI to create new resources or mount or unmount an existing PVC. diff --git a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/upgrading-from-2-x-or-3-x-to-4-x.md b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/upgrading-from-2-x-or-3-x-to-4-x.md index c2f0e9e..3884b39 100644 --- a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/upgrading-from-2-x-or-3-x-to-4-x.md +++ b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/upgrading-from-2-x-or-3-x-to-4-x.md @@ -5,7 +5,7 @@ description: weight: 1 --- ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >In CSI 2._x_ or 3._x_, when block storage is used, the mapping with storage is set up in the huawei-csi-node service. Therefore, the huawei-csi-node service needs to communicate with the storage management network. Because the huawei-csi-node service is deployed as a DaemonSet, the huawei-csi-node service is deployed on each node in the cluster. As a result, in a large-scale cluster, each huawei-csi-node service sends requests to the storage and the number of storage connections may be fully occupied. Accordingly, huawei-csi-node cannot provide services properly. >In CSI 4._x_, the deployment model is optimized. The setup of the mapping with storage is migrated to the huawei-csi-controller service and the huawei-csi-node service does not need to communicate with the storage management network. This reduces the networking complexity of Huawei CSI. In addition, the huawei-csi-controller service is deployed as a Deployment. The number of copies is set based on the customer's reliability requirements. Generally, the number of copies ranges from 1 to 3. Therefore, the number of connections between Huawei CSI and storage is greatly reduced, so that Huawei CSI can connect to a large-scale cluster. >This change may cause a problem. That is, if a new mount process is generated after CSI is upgraded to 4._x_ but with workloads provisioned using 2._x_ or 3._x_ and the Container Orchestration \(CO\) system does not invoke the huawei-csi-controller service provided by Huawei CSI, the mounting will fail. For details, see [A Pod Fails to Be Created and Message "publishInfo doesn't exist" Is Displayed in the Events Log](/docs/troubleshooting/pod-issues/a-pod-fails-to-be-created-and-message-publishinfo-doesn-t-exist-is-displayed-in-the-events-log). diff --git a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/upgrading-huawei-csi-on-kubernetes-openshift-and-tanzu.md b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/upgrading-huawei-csi-on-kubernetes-openshift-and-tanzu.md index 7ac862b..5f13021 100644 --- a/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/upgrading-huawei-csi-on-kubernetes-openshift-and-tanzu.md +++ b/content/en/docs/installation-and-deployment/upgrading-or-rolling-back-huawei-csi/upgrading-or-rolling-back-huawei-csi-using-helm/upgrading-huawei-csi/upgrading-huawei-csi-on-kubernetes-openshift-and-tanzu.md @@ -135,7 +135,7 @@ If CSI of an earlier version is deployed using Helm, perform the following steps 8. \(Optional\) If you need to update configuration items or add configuration information during the upgrade, modify the configuration information in the **update-values.yaml** file by referring to [Parameters in the values.yaml File of Helm](/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/parameters-in-the-values-yaml-file-of-helm). - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >During the upgrade, if the **update-values.yaml** and **values.yaml** configuration files contain the same configuration item, the configuration in the **update-values.yaml** file takes effect preferentially. 9. Run the following command to upgrade Huawei CSI. In the following command, **helm-huawei-csi** indicates the specified Helm chart name, **huawei-csi** indicates the specified Helm chart namespace, and **update-values.yaml** indicates the file obtained in [6](#li1037712113474). diff --git a/content/en/docs/overview/_index.md b/content/en/docs/overview/_index.md index edb9ace..5e29e28 100644 --- a/content/en/docs/overview/_index.md +++ b/content/en/docs/overview/_index.md @@ -10,7 +10,7 @@ weight: 2 Kubernetes uses a series of officially maintained sidecar components to register and listen to Kubernetes object resources and call CSI Driver through gRPC when necessary. Huawei CSI Driver implements the call initiated by sidecar on Huawei storage, for example, creating a [Persistent Volume \(PV\)](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) is to create a LUN or file system on Huawei storage. The following figure shows the overall structure of Kubernetes, Huawei CSI, and Huawei storage. **Figure 1** CSI overall architecture -![](/figures/csi-overall-architecture.png "csi-overall-architecture") +![](/css-docs/figures/csi-overall-architecture.png "csi-overall-architecture") Huawei CSI consists of two components: huawei-csi-controller and huawei-csi-node. @@ -20,7 +20,7 @@ Huawei CSI consists of two components: huawei-csi-controller and huawei-csi-node The following figure shows the deployment model of Huawei CSI. **Figure 2** CSI deployment model -![](/figures/csi-deployment-model.png "csi-deployment-model") +![](/css-docs/figures/csi-deployment-model.png "csi-deployment-model") This document describes how to install, deploy, and use the Huawei CSI V4.5.0 plug-in. diff --git a/content/en/docs/quick-start/_index.md b/content/en/docs/quick-start/_index.md index dced0ac..671209f 100644 --- a/content/en/docs/quick-start/_index.md +++ b/content/en/docs/quick-start/_index.md @@ -10,7 +10,7 @@ This chapter describes how to quickly install and use Huawei CSI to manage Persi ## Huawei CSI Use Process{#section10356165115616} **Figure 1** CSI installation and use process -![](/figures/csi-installation-and-use-process.png "csi-installation-and-use-process") +![](/css-docs/figures/csi-installation-and-use-process.png "csi-installation-and-use-process") ## Compatibility and Features{#section17589135519713} diff --git a/content/en/docs/storage-backend-management/description-of-oceanctl-commands.md b/content/en/docs/storage-backend-management/description-of-oceanctl-commands.md index a4c54be..c95e9ab 100644 --- a/content/en/docs/storage-backend-management/description-of-oceanctl-commands.md +++ b/content/en/docs/storage-backend-management/description-of-oceanctl-commands.md @@ -59,7 +59,7 @@ weight: 3 - Run the following command to create a storage backend and specify **provisioner**. **csi.oceanstor.com** is the driver name specified during installation. For details, see [4](/docs/installation-and-deployment/installing-huawei-csi/installing-huawei-csi-using-helm/installing-huawei-csi-on-the-cce-or-cce-agile-platform#li4307135252018). - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >This command is used only when a backend is created on the CCE or CCE Agile platform. ``` diff --git a/content/en/docs/storage-backend-management/managing-storage-backends/creating-a-storage-backend/_index.md b/content/en/docs/storage-backend-management/managing-storage-backends/creating-a-storage-backend/_index.md index c16f46e..95f33fb 100644 --- a/content/en/docs/storage-backend-management/managing-storage-backends/creating-a-storage-backend/_index.md +++ b/content/en/docs/storage-backend-management/managing-storage-backends/creating-a-storage-backend/_index.md @@ -5,7 +5,7 @@ description: weight: 1 --- ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >1. When oceanctl is used to create a storage backend, the entered account and key information is stored in the [Secret](https://kubernetes.io/docs/concepts/configuration/secret/) object. It is recommended that the customer container platform encrypt the Secret object based on the suggestions of the supplier or K8s community. For details about how to encrypt the Secret object in the K8s community, see [Enable Encryption at Rest](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/). >2. When a backend is created using a .json file, the backend name of an earlier version may contain uppercase letters or underscores \(\_\). In this case, the old name is remapped to a new name. The mapping process automatically occurs and does not affect the original functions. For example, **ABC\_123** is mapped to **abc-123-fd68e**. The mapping rules are as follows: > - Uppercase letters are converted to lowercase letters. diff --git a/content/en/docs/storage-backend-management/managing-storage-backends/creating-a-storage-backend/examples-of-storage-backend-configuration-files-in-typical-scenarios.md b/content/en/docs/storage-backend-management/managing-storage-backends/creating-a-storage-backend/examples-of-storage-backend-configuration-files-in-typical-scenarios.md index 9242bcf..6c44945 100644 --- a/content/en/docs/storage-backend-management/managing-storage-backends/creating-a-storage-backend/examples-of-storage-backend-configuration-files-in-typical-scenarios.md +++ b/content/en/docs/storage-backend-management/managing-storage-backends/creating-a-storage-backend/examples-of-storage-backend-configuration-files-in-typical-scenarios.md @@ -19,7 +19,7 @@ For details about the backend configuration in typical scenarios, see the follow ## Configuring a Storage Backend of the iSCSI Type{#section9560112218344} ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >If you want to use the iSCSI protocol, ensure that the iSCSI client has been installed on the host before installing Huawei CSI. You can check whether the client has been installed on the host by referring to [Checking the Status of Host-Dependent Software](/docs/installation-and-deployment/installation-preparations/checking-the-status-of-host-dependent-software). If the iSCSI client is not installed, restart the huawei-csi-node service after installing the iSCSI client. During the restart, do not use Huawei CSI to create new resources or mount or unmount an existing PVC. The following command is used as an example: >``` >kubectl delete pods -n huawei-csi -l app=huawei-csi-node @@ -65,7 +65,7 @@ maxClientThreads: "30" ## Configuring a Storage Backend of the FC Type{#section4385132433717} ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >If you want to use the FC protocol, ensure that the FC network between the host and the storage device is connected before installing Huawei CSI. If the FC network is not connected, connect the FC network and then restart the huawei-csi-node service. During the restart, do not use Huawei CSI to create new resources or mount or unmount an existing PVC. The following command is used as an example: >``` >kubectl delete pods -n huawei-csi -l app=huawei-csi-node @@ -89,7 +89,7 @@ maxClientThreads: "30" ## Configuring a Storage Backend of the NVMe over RoCE Type{#section887724419372} ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >If you want to use the NVMe over RoCE protocol, ensure that the NVMe over RoCE network between the host and the storage device is connected before installing Huawei CSI. If the NVMe over RoCE network is not connected, connect the NVMe over RoCE network and then restart the huawei-csi-node service. During the restart, do not use Huawei CSI to create new resources or mount or unmount an existing PVC. The following command is used as an example: >``` >kubectl delete pods -n huawei-csi -l app=huawei-csi-node @@ -227,7 +227,7 @@ maxClientThreads: "30" ## Configuring Storage Backends of the HyperMetro Type{#section175945335494} ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >- Before configuring NAS HyperMetro, you need to configure the HyperMetro relationship between two storage devices, including the remote device, HyperMetro domain, and the like. The HyperMetro domain of the file system can only work in HyperMetro active-active \(AA\) mode. For details about the configuration operation, see the product documentation of the corresponding storage model. >- The accounts for connecting to NAS HyperMetro backends must be the administrator accounts of the storage vStores. >- Except NAS HyperMetro backends, the management URLs of other backends cannot be the URL of a logical management port of a vStore that has established the HyperMetro relationship. diff --git a/content/en/docs/storage-backend-management/managing-storage-backends/deleting-a-storage-backend.md b/content/en/docs/storage-backend-management/managing-storage-backends/deleting-a-storage-backend.md index 410fb10..6ccfd12 100644 --- a/content/en/docs/storage-backend-management/managing-storage-backends/deleting-a-storage-backend.md +++ b/content/en/docs/storage-backend-management/managing-storage-backends/deleting-a-storage-backend.md @@ -5,7 +5,7 @@ description: weight: 4 --- ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >Do not delete a storage backend when a volume management operation is being performed on it. ## Example of Deleting a Backend{#section20764568435} diff --git a/content/en/docs/storage-backend-management/managing-storage-backends/updating-a-storage-backend/_index.md b/content/en/docs/storage-backend-management/managing-storage-backends/updating-a-storage-backend/_index.md index eed6132..c77faac 100644 --- a/content/en/docs/storage-backend-management/managing-storage-backends/updating-a-storage-backend/_index.md +++ b/content/en/docs/storage-backend-management/managing-storage-backends/updating-a-storage-backend/_index.md @@ -5,7 +5,7 @@ description: weight: 3 --- ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- When oceanctl is used to update storage backend information, only the storage backend password can be updated. >- If the backend account password is updated on the storage device, the CSI plug-in will retry due to login failures. As a result, the account may be locked. If the account is locked, change the password by referring to [An Account Is Locked After the Password Is Updated on the Storage Device](/docs/troubleshooting/storage-backend-issues/an-account-is-locked-after-the-password-is-updated-on-the-storage-device). diff --git a/content/en/docs/storage-backend-management/managing-storage-backends/updating-a-storage-backend/manually-updating-a-storage-backend.md b/content/en/docs/storage-backend-management/managing-storage-backends/updating-a-storage-backend/manually-updating-a-storage-backend.md index 912dca7..e6edd10 100644 --- a/content/en/docs/storage-backend-management/managing-storage-backends/updating-a-storage-backend/manually-updating-a-storage-backend.md +++ b/content/en/docs/storage-backend-management/managing-storage-backends/updating-a-storage-backend/manually-updating-a-storage-backend.md @@ -5,7 +5,7 @@ description: weight: 2 --- ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >- PVC provisioning must be based on a configured storage backend. Therefore, if a PVC has been provisioned on a storage backend, do not change the storage backend. >- The name uniquely identifies a storage backend. The name of a storage backend with a PVC provisioned cannot be changed. >- After a storage backend is modified, the new configuration applies only to volumes to be provisioned. diff --git a/content/en/docs/storage-backend-management/optional-adding-a-certificate-to-a-storage-backend/_index.md b/content/en/docs/storage-backend-management/optional-adding-a-certificate-to-a-storage-backend/_index.md index bf997c0..c88b25a 100644 --- a/content/en/docs/storage-backend-management/optional-adding-a-certificate-to-a-storage-backend/_index.md +++ b/content/en/docs/storage-backend-management/optional-adding-a-certificate-to-a-storage-backend/_index.md @@ -7,7 +7,7 @@ weight: 2 This section describes how to create a certificate for a storage backend. If certificate verification is required for logging in to the storage, you can add a certificate by referring to this section. Currently, you can create a certificate for a storage backend based on the specified .crt or .pem file. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >Before creating a certificate for a storage backend, import the prepared certificate to the storage array. diff --git a/content/en/docs/troubleshooting/huawei-csi-service-issues/failed-to-start-huawei-csi-services-with-the-status-displayed-as-invalidimagename.md b/content/en/docs/troubleshooting/huawei-csi-service-issues/failed-to-start-huawei-csi-services-with-the-status-displayed-as-invalidimagename.md index 9ac95b5..8cde624 100644 --- a/content/en/docs/troubleshooting/huawei-csi-service-issues/failed-to-start-huawei-csi-services-with-the-status-displayed-as-invalidimagename.md +++ b/content/en/docs/troubleshooting/huawei-csi-service-issues/failed-to-start-huawei-csi-services-with-the-status-displayed-as-invalidimagename.md @@ -40,7 +40,7 @@ In the .yaml configuration files of the controller and node, the Huawei CSI imag kubectl edit daemonset huawei-csi-node -o yaml -n=huawei-csi ``` - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >- In **huawei-csi-driver** in the sample .yaml file, modify **image** to Huawei CSI image **huawei-csi:4.5.0**. > ``` > containers: @@ -55,7 +55,7 @@ In the .yaml configuration files of the controller and node, the Huawei CSI imag kubectl edit deployment huawei-csi-controller -o yaml -n=huawei-csi ``` - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >- In **huawei-csi-driver** in the sample .yaml file, modify **image** to Huawei CSI image **huawei-csi:4.5.0**. > ``` > containers: diff --git a/content/en/docs/troubleshooting/storage-backend-issues/a-backend-fails-to-be-created-using-the-oceanctl-tool-and-error-message-context-deadline-exceeded-is.md b/content/en/docs/troubleshooting/storage-backend-issues/a-backend-fails-to-be-created-using-the-oceanctl-tool-and-error-message-context-deadline-exceeded-is.md index 936cc5d..8104cff 100644 --- a/content/en/docs/troubleshooting/storage-backend-issues/a-backend-fails-to-be-created-using-the-oceanctl-tool-and-error-message-context-deadline-exceeded-is.md +++ b/content/en/docs/troubleshooting/storage-backend-issues/a-backend-fails-to-be-created-using-the-oceanctl-tool-and-error-message-context-deadline-exceeded-is.md @@ -65,7 +65,7 @@ Perform the following steps to check whether Huawei CSI fails to verify the conn Contact the Kubernetes platform administrator to check the network between kube-apiserver and CSI webhook. For example, if kube-apiserver has an HTTPS proxy, the CSI webhook service may fail to be accessed. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >In the temporary workaround, the webhook resource will be deleted. This resource is used to check whether the entered account information is correct and whether the connection to the storage can be set up when a storage backend is created. Therefore, deleting this resource affects only the verification during backend creation and does not affect other functions. Pay attention to the following: >- Ensure that the host machine where the huawei-csi-controller service is located can properly communicate with the storage. >- Ensure that the entered account and password are correct. diff --git a/content/en/docs/troubleshooting/storage-backend-issues/a-webhook-fails-to-be-called-when-the-oceanctl-tool-is-used-to-manage-backends.md b/content/en/docs/troubleshooting/storage-backend-issues/a-webhook-fails-to-be-called-when-the-oceanctl-tool-is-used-to-manage-backends.md index 524d0f7..c3dcc91 100644 --- a/content/en/docs/troubleshooting/storage-backend-issues/a-webhook-fails-to-be-called-when-the-oceanctl-tool-is-used-to-manage-backends.md +++ b/content/en/docs/troubleshooting/storage-backend-issues/a-webhook-fails-to-be-called-when-the-oceanctl-tool-is-used-to-manage-backends.md @@ -9,7 +9,7 @@ weight: 1 After the webhook configuration is changed, for example, the value of the **webhookPort** parameter is changed, an error is reported indicating that a webhook fails to be called when the oceanctl tool is used to manage backends, as shown in the following figure. -![](/figures/en-us_image_0000001996023254.png) +![](/css-docs/figures/en-us_image_0000001996023254.png) ## Root Cause Analysis{#en-us_topic_0000001279996521_section1425013451056} diff --git a/content/en/docs/using-huawei-csi/_index.md b/content/en/docs/using-huawei-csi/_index.md index efa4711..106de89 100644 --- a/content/en/docs/using-huawei-csi/_index.md +++ b/content/en/docs/using-huawei-csi/_index.md @@ -7,7 +7,7 @@ weight: 7 This chapter describes how to use Huawei CSI to manage the lifecycle of PVs and snapshots. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- Do not delete a storage backend when using Huawei CSI to manage volumes. >- When block volumes are mapped, Huawei CSI automatically creates associated objects, such as hosts, host groups, and LUN groups, as well as mapping views. If these objects are manually created on the storage, the mapping logic of Huawei CSI will be affected. Therefore, ensure that these objects are deleted before mapping volumes using Huawei CSI. diff --git a/content/en/docs/using-huawei-csi/managing-a-pvc/cloning-a-pvc.md b/content/en/docs/using-huawei-csi/managing-a-pvc/cloning-a-pvc.md index 83fa792..3fa6e6a 100644 --- a/content/en/docs/using-huawei-csi/managing-a-pvc/cloning-a-pvc.md +++ b/content/en/docs/using-huawei-csi/managing-a-pvc/cloning-a-pvc.md @@ -27,7 +27,7 @@ spec: storage: 2Gi ``` ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- The specified **storageClassName** must be the same as the StorageClass of the source volume in **dataSource**. >- The capacity of the clone volume must be greater than or equal to that of the source volume. Equal capacity is recommended. diff --git a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc-using-a-snapshot.md b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc-using-a-snapshot.md index 1681737..858442a 100644 --- a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc-using-a-snapshot.md +++ b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc-using-a-snapshot.md @@ -28,7 +28,7 @@ spec: storage: 100Gi ``` ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- The specified **storageClassName** must be the same as the StorageClass of the snapshot source volume in **dataSource**. >- The capacity of the clone volume must be greater than or equal to that of the snapshot. Equal capacity is recommended. diff --git a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/_index.md b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/_index.md index 4bd8f83..9f567d0 100644 --- a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/_index.md +++ b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/_index.md @@ -72,7 +72,7 @@ To implement dynamic volume provisioning, perform the following steps: mypvc Bound pvc-840054d3-1d5b-4153-b73f-826f980abf9e 100Gi RWO mysc 12s ``` - >![](/public_sys-resources/en/icon-notice.gif) + >![](/css-docs/public_sys-resources/en/icon-notice.gif) >- After the PVC is created, if the PVC is in the **Pending** state after a long time \(for example, one minute\), refer to [When a PVC Is Created, the PVC Is in the Pending State](/docs/troubleshooting/pvc-issues/when-a-pvc-is-created-the-pvc-is-in-the-pending-state). >- You are advised to create or delete a maximum of 100 PVCs in a batch. diff --git a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/storageclass-configuration-examples-in-typical-dynamic-volume-provisioning-scenarios.md b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/storageclass-configuration-examples-in-typical-dynamic-volume-provisioning-scenarios.md index 6822bcb..edbfea0 100644 --- a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/storageclass-configuration-examples-in-typical-dynamic-volume-provisioning-scenarios.md +++ b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/storageclass-configuration-examples-in-typical-dynamic-volume-provisioning-scenarios.md @@ -199,7 +199,7 @@ parameters: qos: '{"IOTYPE": 2, "MINIOPS": 1000}' # Configure QoS. ``` ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >- vStore users of OceanStor V5 cannot configure QoS policies. >- The QoS configuration takes effect only on the newly created PVC. QoS cannot be added automatically for PVCs with the same StorageClass name that have been provisioned. @@ -222,7 +222,7 @@ parameters: authClient: "*" ``` ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >- Before provisioning a NAS HyperMetro volume, you need to configure the HyperMetro relationship between two storage devices, including the remote device, HyperMetro domain, and the like. The HyperMetro domain of the file system can only work in HyperMetro active-active \(AA\) mode. For details about the configuration operation, see the product documentation of the corresponding storage model. >- If a storage device is faulty, the logical management port may fail over. In this case, you need to manually clear the corresponding storage resources after deleting the NAS HyperMetro volume. @@ -269,7 +269,7 @@ After the StorageClass configuration is complete, perform the following steps to After creating a StorageClass, you can use the StorageClass to create a PV or PVC. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >Pay attention to the following when using a StorageClass: >- Modifications to a StorageClass do not take effect on existing PVs. You need to delete these PVs and create them again using the modified StorageClass to apply the modified parameters. diff --git a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/manage-volume-provisioning/_index.md b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/manage-volume-provisioning/_index.md index d2ed5af..d969e5c 100644 --- a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/manage-volume-provisioning/_index.md +++ b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/manage-volume-provisioning/_index.md @@ -11,7 +11,7 @@ Manage Volume Provisioning allows administrators to use resources created on sto - The Kubernetes cluster is rebuilt. - Storage data is migrated in disaster recovery \(DR\) scenarios. ->![](/public_sys-resources/en/icon-note.gif) +>![](/css-docs/public_sys-resources/en/icon-note.gif) >In scenarios where multiple Kubernetes clusters are deployed, when Manage Volume Provisioning is used to manage the same storage resource, management operations performed on the PVC corresponding to the resource in any cluster will not be synchronized to other clusters. >For example, when you expand the capacity of a PVC in a cluster, the capacity of the corresponding PVC in other clusters will not be automatically expanded. In this case, you need to manually expand the capacity in other clusters by running the expansion commands in [Expanding the Capacity of a PVC](/docs/using-huawei-csi/managing-a-pvc/expanding-the-capacity-of-a-pvc). @@ -85,7 +85,7 @@ Manage Volume Provisioning allows administrators to use resources created on sto mypvc Bound pvc-840054d3-1d5b-4153-b73f-826f980abf9e 100Gi RWO mysc 12s ``` - >![](/public_sys-resources/en/icon-notice.gif) + >![](/css-docs/public_sys-resources/en/icon-notice.gif) >- After the PVC is created, if the PVC is in the **Pending** state after a long time \(for example, one minute\), refer to [When a PVC Is Created, the PVC Is in the Pending State](/docs/troubleshooting/pvc-issues/when-a-pvc-is-created-the-pvc-is-in-the-pending-state). >- You are advised to create or delete a maximum of 100 PVCs in a batch. diff --git a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/manage-volume-provisioning/storageclass-configuration-examples-in-typical-manage-volume-provisioning-scenarios.md b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/manage-volume-provisioning/storageclass-configuration-examples-in-typical-manage-volume-provisioning-scenarios.md index 2bd3318..6e558ca 100644 --- a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/manage-volume-provisioning/storageclass-configuration-examples-in-typical-manage-volume-provisioning-scenarios.md +++ b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/manage-volume-provisioning/storageclass-configuration-examples-in-typical-manage-volume-provisioning-scenarios.md @@ -149,7 +149,7 @@ After the StorageClass configuration is complete, perform the following steps to After creating a StorageClass, you can use the StorageClass to create a PV or PVC. ->![](/public_sys-resources/en/icon-notice.gif) +>![](/css-docs/public_sys-resources/en/icon-notice.gif) >In the Manage Volume Provisioning mode, pay attention to the following when using a StorageClass: >- Modifications to a StorageClass do not take effect on existing PVs. You need to delete these PVs and create them again using the modified StorageClass to apply the modified parameters. diff --git a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/static-volume-provisioning/_index.md b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/static-volume-provisioning/_index.md index 75766b7..9ac508b 100644 --- a/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/static-volume-provisioning/_index.md +++ b/content/en/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/static-volume-provisioning/_index.md @@ -38,7 +38,7 @@ A storage resource, such as a LUN or file system, required by the PV to be creat storage: 100Gi ``` - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >In the configuration file for static volume provisioning, **storageClassName** must be set to **""**. Otherwise, Kubernetes will use the default StorageClass. 2. Run the following command to create a PV based on the prepared .yaml file. @@ -101,7 +101,7 @@ After a PV is created in static volume provisioning mode, you can create a PVC b mypvc Bound pvc-840054d3-1d5b-4153-b73f-826f980abf9e 100Gi RWO 12s ``` - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >- After the PVC is created, if the PVC is in the **Pending** state after a long time \(for example, one minute\), refer to [When a PVC Is Created, the PVC Is in the Pending State](/docs/troubleshooting/pvc-issues/when-a-pvc-is-created-the-pvc-is-in-the-pending-state). >- You are advised to create or delete a maximum of 100 PVCs in a batch. diff --git a/content/en/docs/using-huawei-csi/managing-a-pvc/expanding-the-capacity-of-a-pvc.md b/content/en/docs/using-huawei-csi/managing-a-pvc/expanding-the-capacity-of-a-pvc.md index 3e3169e..99135f2 100644 --- a/content/en/docs/using-huawei-csi/managing-a-pvc/expanding-the-capacity-of-a-pvc.md +++ b/content/en/docs/using-huawei-csi/managing-a-pvc/expanding-the-capacity-of-a-pvc.md @@ -68,7 +68,7 @@ When the capacity of a PVC used by a container is insufficient, you need to expa In the preceding command, _mypvc_ indicates the name of the PVC to be expanded, and _120Gi_ indicates the capacity after expansion. Change the values based on the site requirements. - >![](/public_sys-resources/en/icon-note.gif) + >![](/css-docs/public_sys-resources/en/icon-note.gif) >- The PVC capacity depends on storage specifications and host specifications. For example, OceanStor Dorado 6.1.2 or OceanStor Pacific series 8.1.0 is connected to CentOS 7. If ext4 file systems are used, see [Table 2](/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/pvc-parameters-for-dynamic-volume-provisioning#en-us_topic_0150885187_table178824527142). If XFS file systems are used, see [Table 3](/docs/using-huawei-csi/managing-a-pvc/creating-a-pvc/dynamic-volume-provisioning/pvc-parameters-for-dynamic-volume-provisioning#en-us_topic_0150885187_table101951367104). If NFS or raw devices are used, the capacity must meet the specifications of the used Huawei storage device model and version. >- If the PVC capacity does not meet the specifications, a PVC or Pod may fail to be created due to the limitations of storage specifications or host file system specifications. >- If the capacity expansion fails because the target capacity exceeds the storage pool capacity, see [Failed to Expand the PVC Capacity Because the Target Capacity Exceeds the Storage Pool Capacity](/docs/troubleshooting/pvc-issues/failed-to-expand-the-pvc-capacity-because-the-target-capacity-exceeds-the-storage-pool-capacity). diff --git "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\344\273\216\345\277\253\347\205\247\345\210\233\345\273\272PVC.md" "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\344\273\216\345\277\253\347\205\247\345\210\233\345\273\272PVC.md" index c390e1b..a07e7ff 100644 --- "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\344\273\216\345\277\253\347\205\247\345\210\233\345\273\272PVC.md" +++ "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\344\273\216\345\277\253\347\205\247\345\210\233\345\273\272PVC.md" @@ -28,7 +28,7 @@ spec: storage: 100Gi ``` ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 指定的storageClassName必须和dataSource中的快照源卷的StorageClass需一致。 >- 克隆卷的容量必须不小于快照容量，建议和快照容量保持一致。 diff --git "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\205\213\351\232\206PVC.md" "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\205\213\351\232\206PVC.md" index 7440773..0057b08 100644 --- "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\205\213\351\232\206PVC.md" +++ "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\205\213\351\232\206PVC.md" @@ -27,7 +27,7 @@ spec: storage: 2Gi ``` ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 指定的storageClassName必须和dataSource中的源卷的StorageClass需一致。 >- 克隆卷的容量必须不小于源卷容量，建议和源卷容量保持一致。 diff --git "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224/_index.md" "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224/_index.md" index e3a7377..3d37198 100644 --- "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224/_index.md" +++ "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224/_index.md" @@ -72,7 +72,7 @@ weight: 1 mypvc Bound pvc-840054d3-1d5b-4153-b73f-826f980abf9e 100Gi RWO mysc 12s ``` - >![](/public_sys-resources/zh/icon-notice.gif) + >![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 完成创建PVC操作后，如果长时间后（如一分钟后）PVC的状态是Pending，请参考[创建PVC时， PVC的状态为Pending](/docs/故障处理/PVC相关问题/创建PVC时-PVC的状态为Pending)。 >- 建议每批次最多批量创建/删除100个PVC。 diff --git "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224\345\205\270\345\236\213\345\234\272\346\231\257StorageClass\351\205\215\347\275\256\347\244\272\344\276\213.md" "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224\345\205\270\345\236\213\345\234\272\346\231\257StorageClass\351\205\215\347\275\256\347\244\272\344\276\213.md" index 9097f8b..42166b7 100644 --- "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224\345\205\270\345\236\213\345\234\272\346\231\257StorageClass\351\205\215\347\275\256\347\244\272\344\276\213.md" +++ "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224/\345\212\250\346\200\201\345\215\267\344\276\233\345\272\224\345\205\270\345\236\213\345\234\272\346\231\257StorageClass\351\205\215\347\275\256\347\244\272\344\276\213.md" @@ -199,7 +199,7 @@ parameters: qos: '{"IOTYPE": 2, "MINIOPS": 1000}' # 配置QoS ``` ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >- OceanStor V5 租户用户不支持配置QoS策略。 >- 配置QoS后只能在新建的PVC上生效；对于同名StorageClass已经发放的PVC，不能自动添加QoS @@ -222,7 +222,7 @@ parameters: authClient: "*" ``` ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 发放NAS双活卷前，需要在两台存储设备之间配置双活关系，包含远端设备、双活域等，仅支持文件系统双活域工作模式为双活AA模式，配置操作请参考对应存储型号的产品文档。 >- 若存储发生故障，逻辑管理端口可能产生漂移，在漂移状态下删除NAS双活卷后，需手动清理对应的存储资源。 @@ -269,7 +269,7 @@ parameters: 创建StorageClass后，就可以使用该StorageClass进行创建PV或者PVC。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >在StorageClass的使用中请注意如下事项： >- **针对StorageClass进行的修改将不会在已经创建的PV上生效。您需要删除这些PV，并重新使用修改后的StorageClass创建才能应用修改的参数。** diff --git "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224/_index.md" "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224/_index.md" index 72f22cd..6daa250 100644 --- "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224/_index.md" +++ "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224/_index.md" @@ -11,7 +11,7 @@ weight: 2 - 重建Kubernetes集群。 - 容灾场景下，对存储数据进行迁移。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >在多Kubernetes集群场景下，使用纳管卷特性对同一存储资源进行管理时，在任一集群中对该资源对应的PVC进行管理操作后，不会同步到其他集群中。 >例如：在某一集群中对PVC进行扩容时，其他集群对应的PVC不会自动扩容，需要在其他集群中手动根据[扩容PVC](/docs/使用华为CSI/PVC管理/扩容PVC)中的扩容命令进行扩容。 @@ -85,7 +85,7 @@ weight: 2 mypvc Bound pvc-840054d3-1d5b-4153-b73f-826f980abf9e 100Gi RWO mysc 12s ``` - >![](/public_sys-resources/zh/icon-notice.gif) + >![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 完成创建PVC操作后，如果长时间后（如一分钟后）PVC的状态是Pending，请参考[创建PVC时， PVC的状态为Pending](/docs/故障处理/PVC相关问题/创建PVC时-PVC的状态为Pending)。 >- 建议每批次最多批量创建/删除100个PVC。 diff --git "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224\345\205\270\345\236\213\345\234\272\346\231\257StorageClass\351\205\215\347\275\256\347\244\272\344\276\213.md" "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224\345\205\270\345\236\213\345\234\272\346\231\257StorageClass\351\205\215\347\275\256\347\244\272\344\276\213.md" index e21d24d..62e9868 100644 --- "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224\345\205\270\345\236\213\345\234\272\346\231\257StorageClass\351\205\215\347\275\256\347\244\272\344\276\213.md" +++ "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224/\347\272\263\347\256\241\345\215\267\344\276\233\345\272\224\345\205\270\345\236\213\345\234\272\346\231\257StorageClass\351\205\215\347\275\256\347\244\272\344\276\213.md" @@ -149,7 +149,7 @@ parameters: 创建StorageClass后，就可以使用该StorageClass进行创建PV或者PVC。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >在纳管卷供应场景下，StorageClass的使用中请注意如下事项： >- **针对StorageClass进行的修改将不会在已经创建的PV上生效。您需要删除这些PV，并重新使用修改后的StorageClass创建才能应用修改的参数。** diff --git "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\351\235\231\346\200\201\345\215\267\344\276\233\345\272\224/_index.md" "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\351\235\231\346\200\201\345\215\267\344\276\233\345\272\224/_index.md" index a42b2d1..71b71f8 100644 --- "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\351\235\231\346\200\201\345\215\267\344\276\233\345\272\224/_index.md" +++ "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\345\210\233\345\273\272PVC/\351\235\231\346\200\201\345\215\267\344\276\233\345\272\224/_index.md" @@ -38,7 +38,7 @@ weight: 3 storage: 100Gi ``` - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >静态卷供应的配置文件中，storageClassName参数必须配置为‘“”’，如果不配置，Kubernetes会使用系统默认的StorageClass。 2. 执行以下命令，基于准备好的yaml文件创建PV。 @@ -101,7 +101,7 @@ weight: 3 mypvc Bound pvc-840054d3-1d5b-4153-b73f-826f980abf9e 100Gi RWO 12s ``` - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >- 完成创建PVC操作后，如果长时间后（如一分钟后）PVC的状态是Pending，请参考[创建PVC时， PVC的状态为Pending](/docs/故障处理/PVC相关问题/创建PVC时-PVC的状态为Pending)。 >- 建议每批次最多批量创建/删除100个PVC。 diff --git "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\346\211\251\345\256\271PVC.md" "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\346\211\251\345\256\271PVC.md" index d6afa53..30e2f5d 100644 --- "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\346\211\251\345\256\271PVC.md" +++ "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/PVC\347\256\241\347\220\206/\346\211\251\345\256\271PVC.md" @@ -68,7 +68,7 @@ weight: 2 其中，"_mypvc_"是需要扩容的PVC名称，“_120Gi_”是扩容后的容量大小。请根据实际情况进行替换。 - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >- PVC容量的规格取决于存储规格限制和主机规格限制。以OceanStor Dorado 6.1.2/OceanStor Pacific系列 8.1.0对接CentOS 7为例，当使用的是ext4文件系统时，容量限制见[表 ext4容量的规格](/docs/使用华为CSI/PVC管理/创建PVC/动态卷供应/动态卷供应PVC参数说明#zh-cn_topic_0150885187_table178824527142)；当使用的是XFS文件系统时，容量限制见[表 XFS容量的规格](/docs/使用华为CSI/PVC管理/创建PVC/动态卷供应/动态卷供应PVC参数说明#zh-cn_topic_0150885187_table101951367104)。如果使用的是NFS或者裸设备，容量需满足使用的华为存储设备型号和版本所要求的规格约束。 >- 如果PVC容量不在规格范围内，可能会由于存储规格限制或主机文件系统规格限制导致创建PVC或Pod失败。 >- 如果扩容的目标容量超过存储池容量导致扩容失败，请参考[PVC扩容的目标容量超过存储池容量导致扩容失败](/docs/故障处理/PVC相关问题/PVC扩容的目标容量超过存储池容量导致扩容失败)。 diff --git "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/_index.md" "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/_index.md" index 13c8000..38ee70f 100644 --- "a/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/_index.md" +++ "b/content/zh-cn/docs/\344\275\277\347\224\250\345\215\216\344\270\272CSI/_index.md" @@ -7,7 +7,7 @@ weight: 7 本章节主要介绍如何使用华为CSI对PV、快照的生命周期进行管理。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 使用华为CSI进行卷管理操作期间，请勿删除存储后端。 >- 在映射block卷时，华为CSI会自动创建创建主机、主机组、LUN组等这些卷映射需要的关联对象，以及映射视图。如果手动在存储上创建了这些对象，会影响华为CSI的映射逻辑，请确保在使用华为CSI映射卷前删除这些对象。 diff --git "a/content/zh-cn/docs/\345\205\274\345\256\271\346\200\247\345\222\214\347\211\271\346\200\247/Kubernetes\345\217\212\346\223\215\344\275\234\347\263\273\347\273\237\345\205\274\345\256\271\346\200\247.md" "b/content/zh-cn/docs/\345\205\274\345\256\271\346\200\247\345\222\214\347\211\271\346\200\247/Kubernetes\345\217\212\346\223\215\344\275\234\347\263\273\347\273\237\345\205\274\345\256\271\346\200\247.md" index f03c23b..17b469b 100644 --- "a/content/zh-cn/docs/\345\205\274\345\256\271\346\200\247\345\222\214\347\211\271\346\200\247/Kubernetes\345\217\212\346\223\215\344\275\234\347\263\273\347\273\237\345\205\274\345\256\271\346\200\247.md" +++ "b/content/zh-cn/docs/\345\205\274\345\256\271\346\200\247\345\222\214\347\211\271\346\200\247/Kubernetes\345\217\212\346\223\215\344\275\234\347\263\273\347\273\237\345\205\274\345\256\271\346\200\247.md" @@ -47,7 +47,7 @@ weight: 1 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 华为CSI对接Tanzu Kubernetes仅支持集中式存储NAS场景，相关FAQ请参见[对接Tanzu Kubernetes集群常见问题及解决方法](/docs/故障处理/对接Tanzu-Kubernetes集群常见问题及解决方法)。 >- 华为CSI对接CCE/CCE Agile仅支持集中式存储。 @@ -230,7 +230,7 @@ weight: 1 注释3 Anolis OS仅支持OceanStor Pacific存储。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >因DM-Multipath在0.7版本存在执行multipathd show maps时可能无法回显所有的虚拟设备，因此建议使用0.8及以上版本。 >DM-Multipath版本可以通过以下途径查询： >- 如果使用的是rpm包，执行：rpm -qa | grep multipath或rpm -qa | grep device-mapper。 diff --git "a/content/zh-cn/docs/\345\211\215\350\250\200/_index.md" "b/content/zh-cn/docs/\345\211\215\350\250\200/_index.md" index 000c094..3085c7f 100644 --- "a/content/zh-cn/docs/\345\211\215\350\250\200/_index.md" +++ "b/content/zh-cn/docs/\345\211\215\350\250\200/_index.md" @@ -24,28 +24,28 @@ weight: 1 -

+

表示如不避免则将会导致死亡或严重伤害的具有高等级风险的危害。

-

+

表示如不避免则可能导致死亡或严重伤害的具有中等级风险的危害。

-

+

表示如不避免则可能导致轻微或中度伤害的具有低等级风险的危害。

-

+

用于传递设备或环境安全警示信息。如不避免则可能会导致设备损坏、数据丢失、设备性能降低或其它不可预知的结果。

“须知”不涉及人身伤害。

-

+

对正文中重点信息的补充说明。

“说明”不是安全警示信息，不涉及人身、设备及环境伤害信息。

diff --git "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/oceanctl\345\221\275\344\273\244\350\257\264\346\230\216.md" "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/oceanctl\345\221\275\344\273\244\350\257\264\346\230\216.md" index 349dc35..e7e2837 100644 --- "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/oceanctl\345\221\275\344\273\244\350\257\264\346\230\216.md" +++ "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/oceanctl\345\221\275\344\273\244\350\257\264\346\230\216.md" @@ -59,7 +59,7 @@ weight: 3 - 执行以下命令创建存储后端，并指定provisioner，其中“csi.oceanstor.com”是安装时指定的驱动名称，详情可以参考[4](/docs/安装部署/安装华为CSI/使用Helm安装华为CSI/CCE和CCE-Agile平台安装华为CSI#li4307135252018)。 - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >仅在CCE / CCE Agile平台创建后端时使用该命令。 ``` diff --git "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\346\226\260\345\242\236\350\257\201\344\271\246\345\210\260\345\255\230\345\202\250\345\220\216\347\253\257\357\274\210\345\217\257\351\200\211\357\274\211/_index.md" "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\346\226\260\345\242\236\350\257\201\344\271\246\345\210\260\345\255\230\345\202\250\345\220\216\347\253\257\357\274\210\345\217\257\351\200\211\357\274\211/_index.md" index e13305a..5e17aa5 100644 --- "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\346\226\260\345\242\236\350\257\201\344\271\246\345\210\260\345\255\230\345\202\250\345\220\216\347\253\257\357\274\210\345\217\257\351\200\211\357\274\211/_index.md" +++ "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\346\226\260\345\242\236\350\257\201\344\271\246\345\210\260\345\255\230\345\202\250\345\220\216\347\253\257\357\274\210\345\217\257\351\200\211\357\274\211/_index.md" @@ -7,7 +7,7 @@ weight: 2 本章节介绍如何创建证书到存储后端，如果有对服务登录存储添加证书校验的需要，可以参考本章节新增证书，当前支持根据crt文件或者pem文件创建证书到存储后端。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >创建证书到存储后端前，须提前将准备好的证书导入存储阵列。 diff --git "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\233\345\273\272\345\255\230\345\202\250\345\220\216\347\253\257/_index.md" "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\233\345\273\272\345\255\230\345\202\250\345\220\216\347\253\257/_index.md" index 2c6ba26..16b0e35 100644 --- "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\233\345\273\272\345\255\230\345\202\250\345\220\216\347\253\257/_index.md" +++ "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\233\345\273\272\345\255\230\345\202\250\345\220\216\347\253\257/_index.md" @@ -5,7 +5,7 @@ description: weight: 1 --- ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >1. 使用oceanctl创建存储后端时，输入的账号和秘钥信息保存在[Secret](https://kubernetes.io/zh-cn/docs/concepts/configuration/secret/)对象中，建议客户容器平台根据供应商或者K8s社区的建议自行对Secret进行加密。K8s社区对Secret加密可参考[启用静态加密](https://kubernetes.io/zh-cn/docs/tasks/administer-cluster/encrypt-data/)。 >2. 通过json文件创建后端时，旧版本的backend名称中可能存在大写字母或"\_"字符。如果出现这种情况，旧的名称将会被重映射为一个新的名称，映射过程自动发生，不会影响原有功能。例如“ABC\_123”将会被映射为“abc-123-fd68e”，具体映射规则如下： > - 大写字母转换成小写字母。 diff --git "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\233\345\273\272\345\255\230\345\202\250\345\220\216\347\253\257/\345\205\270\345\236\213\345\234\272\346\231\257\345\255\230\345\202\250\345\220\216\347\253\257\351\205\215\347\275\256\346\226\207\344\273\266\347\244\272\344\276\213.md" "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\233\345\273\272\345\255\230\345\202\250\345\220\216\347\253\257/\345\205\270\345\236\213\345\234\272\346\231\257\345\255\230\345\202\250\345\220\216\347\253\257\351\205\215\347\275\256\346\226\207\344\273\266\347\244\272\344\276\213.md" index 7aad3fa..ce7dfa6 100644 --- "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\233\345\273\272\345\255\230\345\202\250\345\220\216\347\253\257/\345\205\270\345\236\213\345\234\272\346\231\257\345\255\230\345\202\250\345\220\216\347\253\257\351\205\215\347\275\256\346\226\207\344\273\266\347\244\272\344\276\213.md" +++ "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\233\345\273\272\345\255\230\345\202\250\345\220\216\347\253\257/\345\205\270\345\236\213\345\234\272\346\231\257\345\255\230\345\202\250\345\220\216\347\253\257\351\205\215\347\275\256\346\226\207\344\273\266\347\244\272\344\276\213.md" @@ -19,7 +19,7 @@ weight: 1 ## 配置iSCSI协议类型的存储后端{#section9560112218344} ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >如果要使用iSCSI协议类型，请确保在安装华为CSI前，主机上已安装iSCSI客户端，可通过[检查主机依赖软件状态](/docs/安装部署/安装前准备/检查主机依赖软件状态)章节检查。如未安装iSCSI客户端，请在安装iSCSI客户端之后重启huawei-csi-node服务，重启期间，不能使用华为CSI创建新的资源，或者对已有的PVC做挂载/卸载操作。参考命令如下： >``` >kubectl delete pods -n huawei-csi -l app=huawei-csi-node @@ -65,7 +65,7 @@ maxClientThreads: "30" ## 配置FC协议类型的存储后端{#section4385132433717} ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >如果要使用FC协议类型，请确保在安装华为CSI前，主机和存储的FC网络已联通，如未FC网络未打通，请在打通FC网络之后重启huawei-csi-node服务，重启期间，不能使用华为CSI创建新的资源，或者对已有的PVC做挂载/卸载操作。参考命令如下： >``` >kubectl delete pods -n huawei-csi -l app=huawei-csi-node @@ -89,7 +89,7 @@ maxClientThreads: "30" ## 配置NVMe over RoCE协议类型的存储后端{#section887724419372} ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >如果要使用NVMe over RoCE协议类型，请确保在安装华为CSI前，主机和存储的NVMe over RoCE网络已联通，如未NVMe over RoCE网络未打通，请在打通NVMe over RoCE网络之后重启huawei-csi-node服务，重启期间，不能使用华为CSI创建新的资源，或者对已有的PVC做挂载/卸载操作。参考命令如下： >``` >kubectl delete pods -n huawei-csi -l app=huawei-csi-node @@ -227,7 +227,7 @@ maxClientThreads: "30" ## 配置双活类型的存储后端{#section175945335494} ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >- 配置NAS双活前，需要在两台存储设备之间配置双活关系，包含远端设备、双活域等，仅支持文件系统双活域工作模式为双活AA模式，配置操作请参考对应存储型号的产品文档。 >- 对接NAS双活后端的账号必须为存储租户的租户管理员账号。 >- 除NAS双活后端外，其他后端的管理URL不能配置为在已建立双活关系的租户的逻辑管理端口的URL。 diff --git "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\240\351\231\244\345\255\230\345\202\250\345\220\216\347\253\257.md" "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\240\351\231\244\345\255\230\345\202\250\345\220\216\347\253\257.md" index 9537664..9fd34e3 100644 --- "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\240\351\231\244\345\255\230\345\202\250\345\220\216\347\253\257.md" +++ "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\345\210\240\351\231\244\345\255\230\345\202\250\345\220\216\347\253\257.md" @@ -5,7 +5,7 @@ description: weight: 4 --- ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >正在执行卷管理操作期间，请勿删除存储后端。 ## 删除后端示例{#section20764568435} diff --git "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257/_index.md" "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257/_index.md" index 8c6da3c..c2d9beb 100644 --- "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257/_index.md" +++ "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257/_index.md" @@ -5,7 +5,7 @@ description: weight: 3 --- ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 当前使用oceanctl更新存储后端信息时，仅支持更新存储后端密码。 >- 若在存储侧更新了后端的账号密码，CSI插件会因登录失败而重试，可能会导致账号被锁定。如果账号被锁定，请参考[存储侧更新密码后账户被锁定](/docs/故障处理/存储后端相关问题/存储侧更新密码后账户被锁定)章节修改。 diff --git "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257/\346\211\213\345\212\250\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257.md" "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257/\346\211\213\345\212\250\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257.md" index 0104cba..60dc248 100644 --- "a/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257/\346\211\213\345\212\250\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257.md" +++ "b/content/zh-cn/docs/\345\255\230\345\202\250\345\220\216\347\253\257\347\256\241\347\220\206/\347\256\241\347\220\206\345\255\230\345\202\250\345\220\216\347\253\257/\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257/\346\211\213\345\212\250\346\233\264\346\226\260\345\255\230\345\202\250\345\220\216\347\253\257.md" @@ -5,7 +5,7 @@ description: weight: 2 --- ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >- PVC发放需要基于已配置的存储后端，因此当存储后端已经发放PVC时，请勿随便修改存储后端。 >- 名称是存储后端的唯一标识，已发放PVC的存储后端不允许修改名称。 >- 存储后端修改后，新增配置仅作用于新发放的卷。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/_index.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/_index.md" index ba252c6..2c500c3 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/_index.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/_index.md" @@ -7,7 +7,7 @@ weight: 4 本章节介绍如何升级/回退华为CSI。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >当前版本华为CSI添加了资源请求和限制，具体详情请参考[华为CSI资源管理](/docs/附录/华为CSI资源管理)。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/Kubernetes-OpenShift-Tanzu\345\215\207\347\272\247\345\215\216\344\270\272CSI.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/Kubernetes-OpenShift-Tanzu\345\215\207\347\272\247\345\215\216\344\270\272CSI.md" index 1a3a5ff..b7c6b8c 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/Kubernetes-OpenShift-Tanzu\345\215\207\347\272\247\345\215\216\344\270\272CSI.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/Kubernetes-OpenShift-Tanzu\345\215\207\347\272\247\345\215\216\344\270\272CSI.md" @@ -135,7 +135,7 @@ weight: 2 8. （可选）在升级过程中如需自定义更新配置项信息或者需要新增配置信息，可参考[Helm values.yaml参数说明](/docs/安装部署/安装华为CSI/使用Helm安装华为CSI/Helm-values-yaml参数说明)修改update-values.yaml文件中配置信息。 - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >升级时，如果update-values.yaml与values.yaml配置文件中存在相同配置项，update-values.yaml中的配置将会优先生效。 9. 执行以下命令，升级华为CSI。其中helm-huawei-csi为指定的Helm Chart名称，huawei-csi为指定的Helm Chart命名空间，update-values.yaml为步骤[6](#li1037712113474)中获取的文件。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/_index.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/_index.md" index 534cba9..b9d4a44 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/_index.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/_index.md" @@ -9,7 +9,7 @@ weight: 1 升级/回退过程中，已经存在的PVC/快照/Pod等资源会正常运行，不会影响您的业务访问。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 部分2.x版本CSI已经下架，若升级失败，可能无法回退到已下架版本的CSI。 >- 从2.x或3.x版本或4.x版本升级至4.5.0版本，可能存在旧版本已发放Pod重新挂载时失败的问题，具体请参考[从2.x或3.x升级至4.x版本](/docs/安装部署/升级-回退华为CSI/使用Helm升级-回退华为CSI/升级华为CSI/从2-x或3-x升级至4-x版本) >- 在升级/回退过程中，不能使用华为CSI创建新的资源，或者对已有的PVC做挂载/卸载操作。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/\344\273\2162-x\346\210\2263-x\345\215\207\347\272\247\350\207\2634-x\347\211\210\346\234\254.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/\344\273\2162-x\346\210\2263-x\345\215\207\347\272\247\350\207\2634-x\347\211\210\346\234\254.md" index e7cd47a..7fbe9a1 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/\344\273\2162-x\346\210\2263-x\345\215\207\347\272\247\350\207\2634-x\347\211\210\346\234\254.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\215\207\347\272\247\345\215\216\344\270\272CSI/\344\273\2162-x\346\210\2263-x\345\215\207\347\272\247\350\207\2634-x\347\211\210\346\234\254.md" @@ -5,7 +5,7 @@ description: weight: 1 --- ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >在CSI 2.x或3.x 版本中，使用块存储时，与存储建立映射的操作是在huawei-csi-node服务进行的，所以huawei-csi-node服务需要和存储管理网络通信。又由于huawei-csi-node服务是以DaemonSet部署的，在集群中每个节点都会部署一个huawei-csi-node服务，这样部署模型导致了在大规模集群下，每个huawei-csi-node服务都会向存储发起请求，可能导致存储连接数被占满，使得huawei-csi-node不能提供正常服务。 >在CSI 4.x版本优化了该部署模型，将与存储建立映射操作迁移至huawei-csi-controller服务，huawei-csi-node服务不再需要和存储管理网络通信，降低了华为CSI依赖的组网复杂度，同时huawei-csi-controller服务以Deployment形式部署，副本数根据客户可靠性要求设置，一般情况下，副本数为1\~3。所以极大的减少了华为CSI与存储的连接数量，使得华为CSI服务能够接入大规模集群。 >**该架构变化可能会导致一个问题**：升级后，使用2.x或3.x发放的工作负载，升级CSI至4.x版本之后，如果产生了一次新的挂载流程，并且CO（Container Orchestration system）未调用华为CSI提供的huawei-csi-controller服务，会导致挂载失败。问题请参考[创建Pod失败，Events日志显示“publishInfo doesn't exist”](/docs/故障处理/Pod相关问题/创建Pod失败-Events日志显示-publishInfo-doesn-t-exist)。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\233\236\351\200\200\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\233\236\351\200\200\345\215\216\344\270\272CSI.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\233\236\351\200\200\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\233\236\351\200\200\345\215\216\344\270\272CSI.md" index a955047..f9c0eb4 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\233\236\351\200\200\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\233\236\351\200\200\345\215\216\344\270\272CSI.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\233\236\351\200\200\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\233\236\351\200\200\345\215\216\344\270\272CSI.md" @@ -5,7 +5,7 @@ description: weight: 2 --- ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 在升级/回退过程中，已经存在的PVC/快照/Pod等资源会正常运行，不会影响您的业务访问。 >- 在升级/回退过程中，不能使用华为CSI创建新的资源，或者对已有的PVC做挂载/卸载操作。 >- 在升级/回退过程中，请勿卸载Snapshot依赖组件服务。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\233\236\351\200\200\345\215\216\344\270\272CSI/_index.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\233\236\351\200\200\345\215\216\344\270\272CSI/_index.md" index 946680e..06819f1 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\233\236\351\200\200\345\215\216\344\270\272CSI/_index.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\345\233\236\351\200\200\345\215\216\344\270\272CSI/_index.md" @@ -7,7 +7,7 @@ weight: 2 如果您从2.x和3.x版本的CSI升级至4.5.0版本失败，需要回退时，请参考[Helm卸载华为CSI](/docs/安装部署/卸载华为CSI/Helm卸载华为CSI)卸载CSI，然后下载安装升级之前版本的CSI。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 在升级/回退过程中，已经存在的PVC/快照/Pod等资源会正常运行，不会影响您的业务访问。 >- 在升级/回退过程中，不能使用华为CSI创建新的资源，或者对已有的PVC做挂载/卸载操作。 >- 在升级/回退过程中，请勿卸载Snapshot依赖组件服务。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\207\347\272\247-\345\233\236\351\200\200/\345\215\207\347\272\247\345\215\216\344\270\272CSI-0.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\207\347\272\247-\345\233\236\351\200\200/\345\215\207\347\272\247\345\215\216\344\270\272CSI-0.md" index ba30a8a..7ce9ff2 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\207\347\272\247-\345\233\236\351\200\200/\345\215\207\347\272\247\345\215\216\344\270\272CSI-0.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\207\347\272\247-\345\233\236\351\200\200/\345\215\207\347\272\247\345\215\216\344\270\272CSI-0.md" @@ -9,7 +9,7 @@ weight: 1 升级/回退过程中，已经存在的PVC/快照/Pod等资源会正常运行，不会影响您的业务访问。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 部分2.x版本CSI已经下架，若升级失败，可能无法回退到已下架版本的CSI。 >- 在升级/回退过程中，不能使用华为CSI创建新的资源，或者对已有的PVC做挂载/卸载操作。 >- 在升级/回退过程中，请勿卸载Snapshot依赖组件服务。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\207\347\272\247-\345\233\236\351\200\200/\345\233\236\351\200\200\345\215\216\344\270\272CSI-1.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\207\347\272\247-\345\233\236\351\200\200/\345\233\236\351\200\200\345\215\216\344\270\272CSI-1.md" index ffdcaaf..7246f29 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\207\347\272\247-\345\233\236\351\200\200/\345\233\236\351\200\200\345\215\216\344\270\272CSI-1.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\207\347\272\247-\345\233\236\351\200\200\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\207\347\272\247-\345\233\236\351\200\200/\345\233\236\351\200\200\345\215\216\344\270\272CSI-1.md" @@ -7,7 +7,7 @@ weight: 2 请参考[手动卸载华为CSI](/docs/安装部署/卸载华为CSI/手动卸载华为CSI)卸载CSI，然后下载安装升级之前版本的CSI。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 在升级/回退过程中，已经存在的PVC/快照/Pod等资源会正常运行，不会影响您的业务访问。 >- 在升级/回退过程中，不能使用华为CSI创建新的资源，或者对已有的PVC做挂载/卸载操作。 >- 在升级/回退过程中，请勿卸载Snapshot依赖组件服务。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/Helm\345\215\270\350\275\275\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\215\270\350\275\275\345\215\216\344\270\272CSI.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/Helm\345\215\270\350\275\275\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\215\270\350\275\275\345\215\216\344\270\272CSI.md" index 505654f..c7e3ffd 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/Helm\345\215\270\350\275\275\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\215\270\350\275\275\345\215\216\344\270\272CSI.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/Helm\345\215\270\350\275\275\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\215\270\350\275\275\345\215\216\344\270\272CSI.md" @@ -13,7 +13,7 @@ weight: 2 2. 在主页单击“模板市场\> 模板实例 ”，进入模板实例页面。 3. 选择华为CSI模板实例，单击“卸载”，在弹出的提示框中单击“确定”。 - ![](/figures/卸载-ch.png) + ![](/css-docs/figures/卸载-ch.png) 4. 卸载huawei-csi-host-info对象，请参考[卸载huawei-csi-host-info对象](/docs/安装部署/卸载华为CSI/Helm卸载华为CSI/卸载CSI依赖组件服务#section870813403017)进行操作。 5. 卸载webhook资源，请参考[卸载Webhook资源](/docs/安装部署/卸载华为CSI/Helm卸载华为CSI/卸载CSI依赖组件服务#section871155813014)进行操作。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/Helm\345\215\270\350\275\275\345\215\216\344\270\272CSI/\345\215\270\350\275\275CSI\344\276\235\350\265\226\347\273\204\344\273\266\346\234\215\345\212\241.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/Helm\345\215\270\350\275\275\345\215\216\344\270\272CSI/\345\215\270\350\275\275CSI\344\276\235\350\265\226\347\273\204\344\273\266\346\234\215\345\212\241.md" index 52965d5..4cad9b3 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/Helm\345\215\270\350\275\275\345\215\216\344\270\272CSI/\345\215\270\350\275\275CSI\344\276\235\350\265\226\347\273\204\344\273\266\346\234\215\345\212\241.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/Helm\345\215\270\350\275\275\345\215\216\344\270\272CSI/\345\215\270\350\275\275CSI\344\276\235\350\265\226\347\273\204\344\273\266\346\234\215\345\212\241.md" @@ -62,7 +62,7 @@ weight: 3 ## 卸载Snapshot依赖组件服务{#section48371491319} ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 请勿在存在快照时卸载Snapshot依赖组件服务，否则Kubernetes会自动删除所有的用户快照且无法恢复，请谨慎操作。详细说明请参见[删除 CustomResourceDefinition](https://kubernetes.io/zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#delete-a-customresourcedefinition)。 >- 请勿在CSI升级时卸载Snapshot依赖组件服务。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/_index.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/_index.md" index f5d3c0e..0fad8da 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/_index.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/_index.md" @@ -7,7 +7,7 @@ weight: 3 本章节介绍如何卸载华为CSI。根据您安装时的方式，请使用不同的方式进行卸载。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >如果您不是出于升级的目的卸载华为CSI，请确保卸载华为CSI前已经在您的容器平台中将华为CSI发放的资源（PV、PVC、快照、存储后端等）全部清理。否则一旦您卸载华为CSI后，这些资源将无法被自动调度、管理或者清理。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\270\350\275\275\345\215\216\344\270\272CSI.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\270\350\275\275\345\215\216\344\270\272CSI.md" index ebce7bf..82c64b7 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\270\350\275\275\345\215\216\344\270\272CSI.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\215\270\350\275\275\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\215\270\350\275\275\345\215\216\344\270\272CSI.md" @@ -7,7 +7,7 @@ weight: 2 本章节介绍如何手动卸载华为CSI。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >如果您不是出于升级的目的卸载华为CSI，请确保卸载华为CSI前已经在您的容器平台中将华为CSI发放的资源（PV、PVC、快照、存储后端等）全部清理。否则一旦您卸载华为CSI后，这些资源将无法被自动调度、管理或者清理。 ## 卸载huawei-csi-node服务{#section1012817231386} diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\344\270\212\344\274\240\345\215\216\344\270\272CSI\351\225\234\345\203\217.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\344\270\212\344\274\240\345\215\216\344\270\272CSI\351\225\234\345\203\217.md" index 2530ac9..ef7a15d 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\344\270\212\344\274\240\345\215\216\344\270\272CSI\351\225\234\345\203\217.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\344\270\212\344\274\240\345\215\216\344\270\272CSI\351\225\234\345\203\217.md" @@ -45,7 +45,7 @@ weight: 2 docker push repo.huawei.com/huawei-csi:4.5.0 ``` ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 也可以使用containerd来进行镜像的导入和上传。 >- CCE / CCE Agile平台请参考该平台用户手册完成镜像导入和上传。 @@ -83,6 +83,6 @@ weight: 2 podman load -i .tar ``` - >![](/public_sys-resources/zh/icon-notice.gif) + >![](/css-docs/public_sys-resources/zh/icon-notice.gif) >当节点主机安装的是其他容器引擎时，请使用对应容器引擎的导入镜像命令。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\344\270\213\350\275\275\345\215\216\344\270\272CSI\350\275\257\344\273\266\345\214\205.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\344\270\213\350\275\275\345\215\216\344\270\272CSI\350\275\257\344\273\266\345\214\205.md" index cdcd04b..eca8428 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\344\270\213\350\275\275\345\215\216\344\270\272CSI\350\275\257\344\273\266\345\214\205.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\344\270\213\350\275\275\345\215\216\344\270\272CSI\350\275\257\344\273\266\345\214\205.md" @@ -10,7 +10,7 @@ weight: 1 1. 打开浏览器，访问仓库地址：[https://github.com/Huawei/eSDK\_K8S\_Plugin/releases](https://github.com/Huawei/eSDK_K8S_Plugin/releases)。 2. 根据CPU架构，下载对应的4.5.0版本软件包。 - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >软件包命名规范：插件名称（eSDK\_Huawei\_Storage\_Kubernetes\_CSI\_Plugin）+版本号+CPU架构 3. 将下载的软件包解压。软件包组件结构如下表所示。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245CSI\344\276\235\350\265\226\347\232\204\351\225\234\345\203\217.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245CSI\344\276\235\350\265\226\347\232\204\351\225\234\345\203\217.md" index 9007ed0..0d67023 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245CSI\344\276\235\350\265\226\347\232\204\351\225\234\345\203\217.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245CSI\344\276\235\350\265\226\347\232\204\351\225\234\345\203\217.md" @@ -140,6 +140,6 @@ huawei-csi-controller服务依赖的sidecar镜像：livenessprobe、csi-provisio ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >集群若未连接互联网，需要手动下载容器镜像并上传到集群中，具体操作请参考[下载容器镜像](/docs/常用操作/下载容器镜像)。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\344\270\273\346\234\272\345\244\232\350\267\257\345\276\204\351\205\215\347\275\256.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\344\270\273\346\234\272\345\244\232\350\267\257\345\276\204\351\205\215\347\275\256.md" index 5dc4502..d4227e0 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\344\270\273\346\234\272\345\244\232\350\267\257\345\276\204\351\205\215\347\275\256.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\344\270\273\346\234\272\345\244\232\350\267\257\345\276\204\351\205\215\347\275\256.md" @@ -9,7 +9,7 @@ weight: 5 华为CSI软件支持对接的操作系统和多路径软件请参考[表 支持的主机操作系统及多路径软件版本](/docs/兼容性和特性/Kubernetes及操作系统兼容性#table133422378818)。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >- 如果您准备使用FC/iSCSI协议对接华为存储时，推荐使用操作系统自带的原生DM-Multipath。 >- 如果您准备使用NVMe over RoCE/NVMe over FC协议对接华为存储时，推荐使用华为自研的UltraPath-NVMe。 >- 如果您使用SCSI协议对接华为存储时，请关闭操作系统自带的DM-Multipath。 @@ -37,6 +37,6 @@ weight: 5 如果配置不存在，请在/etc/multipath.conf文件开始处增加该配置项。 - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >user\_friendly\_names 和find\_multipaths 的参数作用请参考：[dm\_multipath/config\_file\_defaults](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/dm_multipath/config_file_defaults) diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\345\215\216\344\270\272\345\255\230\345\202\250\344\270\212\347\232\204\347\224\250\346\210\267\351\205\215\347\275\256.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\345\215\216\344\270\272\345\255\230\345\202\250\344\270\212\347\232\204\347\224\250\346\210\267\351\205\215\347\275\256.md" index 432a58b..402e172 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\345\215\216\344\270\272\345\255\230\345\202\250\344\270\212\347\232\204\347\224\250\346\210\267\351\205\215\347\275\256.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\345\215\216\344\270\272\345\255\230\345\202\250\344\270\212\347\232\204\347\224\250\346\210\267\351\205\215\347\275\256.md" @@ -100,6 +100,6 @@ weight: 3 - 注释1 使用自定义角色，需要给角色配置权限，最小权限请参考[配置自定义权限](/docs/附录/配置自定义权限)章节配置。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >不推荐使用“超级管理员”角色下的用户。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\345\215\267\345\277\253\347\205\247\344\276\235\350\265\226\347\273\204\344\273\266.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\345\215\267\345\277\253\347\205\247\344\276\235\350\265\226\347\273\204\344\273\266.md" index b1ba5be..ef33a2b 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\345\215\267\345\277\253\347\205\247\344\276\235\350\265\226\347\273\204\344\273\266.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\211\215\345\207\206\345\244\207/\346\243\200\346\237\245\345\215\267\345\277\253\347\205\247\344\276\235\350\265\226\347\273\204\344\273\266.md" @@ -7,7 +7,7 @@ weight: 4 本章节介绍如何检查集群中卷快照依赖组件情况。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >由于Kubernetes v1.17.0之前不支持快照功能，如果部署快照CRD可能导致集群出现问题，因此在低于Kubernetes v1.17.0版本上部署华为CSI，请务必按照[Kubernetes低于v1.17.0](#section6894165917369)章节检查。 ## Kubernetes低于v1.17.0{#section6894165917369} diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/_index.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/_index.md" index c5c0846..a7c7cba 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/_index.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/_index.md" @@ -7,7 +7,7 @@ weight: 2 本章节介绍如何安装华为CSI。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >当前版本华为CSI添加了资源请求和限制，具体详情请参考[华为CSI资源管理](/docs/附录/华为CSI资源管理)。 ## 前提条件{#zh-cn_topic_0000001324610777_section19453102010152} diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\271\263\345\217\260\345\256\211\350\243\205\345\215\216\344\270\272CSI.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\271\263\345\217\260\345\256\211\350\243\205\345\215\216\344\270\272CSI.md" index 1015c09..9d8a04f 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\271\263\345\217\260\345\256\211\350\243\205\345\215\216\344\270\272CSI.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/CCE\345\222\214CCE-Agile\345\271\263\345\217\260\345\256\211\350\243\205\345\215\216\344\270\272CSI.md" @@ -59,13 +59,13 @@ CCE和CCE Agile平台无法直接通过Helm安装华为CSI，需要手动制作H 3. 导出Helm安装包，具体请参考[制作Helm安装包](#section2032812215509)。 4. 在主页单击“模板市场\> 我的模板\>上传模板”，进入上传模板对话框。将导出的Helm安装包导入CCE Agile平台。 - ![](/figures/上传模板-ch.png) + ![](/css-docs/figures/上传模板-ch.png) 5. 安装包上传完毕，在主页单击“模板市场\>我的模板”，进入我的模板页面，单击“安装\>提交”。其中模板实例名称可自定义填写。 - ![](/figures/安装csi中文.png) + ![](/css-docs/figures/安装csi中文.png) 6. 在主页单击“模板市场\>模板实例”，选择安装时指定的项目（例如样例中的项目是“default”）。安装成功后执行状态将回显为“安装成功”。 - ![](/figures/安装结果-ch.png) + ![](/css-docs/figures/安装结果-ch.png) diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/Helm-values-yaml\345\217\202\346\225\260\350\257\264\346\230\216.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/Helm-values-yaml\345\217\202\346\225\260\350\257\264\346\230\216.md" index ef96a7e..c6404b4 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/Helm-values-yaml\345\217\202\346\225\260\350\257\264\346\230\216.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/Helm-values-yaml\345\217\202\346\225\260\350\257\264\346\230\216.md" @@ -128,7 +128,7 @@ values.yaml中的images配置项主要配置华为CSI运行时依赖的组件镜 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- huaweiCSIService、storageBackendSidecar、storageBackendController、huaweiCSIExtender参数的值，请参考[上传华为CSI镜像](/docs/安装部署/安装前准备/上传华为CSI镜像)章节的说明，使用最终生成镜像的名称和版本。 >- 其他sidecar镜像参数，请参考[检查CSI依赖的镜像](/docs/安装部署/安装前准备/检查CSI依赖的镜像)章节的说明，使用最终上传的镜像的名称和版本。 @@ -290,7 +290,7 @@ controller配置项用于配置huawei-csi-controller组件的相关配置。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >当controller.snapshot.enabled参数配置为true时，需要安装“helm/crd/snapshot-crds”目录下的卷快照CRD资源。 ## node参数配置说明{#section374014171581} @@ -630,7 +630,7 @@ csiDriver配置项包括了华为CSI运行时的基本配置，如华为驱动 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >如果您的容器环境已经部署了华为CSI，请确保csiDriver.driverName的设置和之前部署时的配置保持一致。否则会导致系统中已存在的有华为CSI发放的卷/快照无法被新部署的华为CSI管理。 ## 其他参数配置说明{#section11500468593} @@ -770,7 +770,7 @@ csiDriver配置项包括了华为CSI运行时的基本配置，如华为驱动 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >请确保此kubernetes.namespace填入的命名空间在Kubernetes上已经存在，如果不存在请使用如下命令创建对应的命名空间。本例中，华为CSI运行的命名空间为“huawei-csi”。 >``` >kubectl create namespace huawei-csi diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/_index.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/_index.md" index 7bcbfbb..bd58299 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/_index.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\344\275\277\347\224\250Helm\345\256\211\350\243\205\345\215\216\344\270\272CSI/_index.md" @@ -9,7 +9,7 @@ weight: 1 本章节介绍如何使用Helm 3安装部署华为CSI。 ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 华为CSI的安装支持root用户和非root用户。使用非root用户安装华为CSI时，需要保证当前用户能够访问Kubernetes集群的API Server，配置非root用户访问Kubernetes集群请参考[配置非root用户访问Kubernetes集群](/docs/常用操作/配置非root用户访问Kubernetes集群)。 >- 华为CSI必须在root用户权限下运行。 diff --git "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\256\211\350\243\205\345\215\216\344\270\272CSI.md" "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\256\211\350\243\205\345\215\216\344\270\272CSI.md" index 051a5d5..401b815 100644 --- "a/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\256\211\350\243\205\345\215\216\344\270\272CSI.md" +++ "b/content/zh-cn/docs/\345\256\211\350\243\205\351\203\250\347\275\262/\345\256\211\350\243\205\345\215\216\344\270\272CSI/\346\211\213\345\212\250\345\256\211\350\243\205\345\215\216\344\270\272CSI.md" @@ -7,7 +7,7 @@ weight: 2 本章节介绍如何手动安装华为CSI。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >手动安装华为CSI当前仅支持Kubernetes平台。 ## 安装步骤{#section113761618183018} @@ -72,7 +72,7 @@ weight: 2 huawei-csi-node-xrntc 3/3 Running 0 13m ``` ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >多副本controller部署场景下可以通过修改 _./deploy/huawei-csi-controller.yaml_ 文件中Deployment资源的spec.replica字段来指定副本个数，修改完成后，执行以下命令生效： >``` >kubectl apply -f ./deploy/huawei-csi-controller.yaml diff --git "a/content/zh-cn/docs/\345\270\270\347\224\250\346\223\215\344\275\234/\345\274\200\345\220\257ReadWriteOncePod\345\212\237\350\203\275\351\227\250.md" "b/content/zh-cn/docs/\345\270\270\347\224\250\346\223\215\344\275\234/\345\274\200\345\220\257ReadWriteOncePod\345\212\237\350\203\275\351\227\250.md" index 156763e..e377002 100644 --- "a/content/zh-cn/docs/\345\270\270\347\224\250\346\223\215\344\275\234/\345\274\200\345\220\257ReadWriteOncePod\345\212\237\350\203\275\351\227\250.md" +++ "b/content/zh-cn/docs/\345\270\270\347\224\250\346\223\215\344\275\234/\345\274\200\345\220\257ReadWriteOncePod\345\212\237\350\203\275\351\227\250.md" @@ -9,7 +9,7 @@ ReadWriteOnce访问模式是Kubernetes v1.22版本为PV和PVC引入的第四种 由于ReadWriteOncePod访问模式在当前已发布的Kubernetes v1.22/1.23/1.24版本中是alpha特性，需要先在kube-apiserver、kube-scheduler和kubelet的feature-gates中开启ReadWriteOncePod特性才能使用。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >CCE / CCE Agile平台暂时不支持开启ReadWriteOncePod功能门 ## 操作步骤{#zh-cn_topic_0000001259843616_section137882216292} @@ -28,7 +28,7 @@ ReadWriteOnce访问模式是Kubernetes v1.22版本为PV和PVC引入的第四种 ... ``` - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >在编辑完成后，Kubernetes会自动应用更新，不需要手动更新。 2. 为kube-scheduler启用ReadWriteOncePod功能门。 @@ -45,12 +45,12 @@ ReadWriteOnce访问模式是Kubernetes v1.22版本为PV和PVC引入的第四种 ... ``` - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >在编辑完成后，Kubernetes会自动应用更新，不需要手动更新。 3. 为kubelet启用ReadWriteOncePod功能门。 - >![](/public_sys-resources/zh/icon-notice.gif) + >![](/css-docs/public_sys-resources/zh/icon-notice.gif) >由于动态Kubelet配置功能在v1.22中已弃用，并且在v1.24中删除，因此集群中每个worker节点上的kubelet都需要执行以下操作。 1. 使用远程访问工具（以PuTTY为例），通过管理IP地址，登录Kubernetes集群的任意worker节点。 @@ -63,7 +63,7 @@ ReadWriteOnce访问模式是Kubernetes v1.22版本为PV和PVC引入的第四种 ... ``` - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >kubelet配置文件的默认路径为/var/lib/kubelet/config.yaml，请根据实际情况填写。 3. 在配置完成后，执行**systemctl restart kubelet**命令重启kubelet。 diff --git "a/content/zh-cn/docs/\345\277\253\351\200\237\345\274\200\345\247\213/_index.md" "b/content/zh-cn/docs/\345\277\253\351\200\237\345\274\200\345\247\213/_index.md" index 111cf8e..e28bbbc 100644 --- "a/content/zh-cn/docs/\345\277\253\351\200\237\345\274\200\345\247\213/_index.md" +++ "b/content/zh-cn/docs/\345\277\253\351\200\237\345\274\200\345\247\213/_index.md" @@ -10,7 +10,7 @@ weight: 3 ## 华为CSI使用流程概览{#section10356165115616} **图 1** CSI安装及使用流程图 -![](/figures/CSI安装及使用流程图.png "CSI安装及使用流程图") +![](/css-docs/figures/CSI安装及使用流程图.png "CSI安装及使用流程图") ## 兼容性和特性{#section17589135519713} diff --git "a/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\215\216\344\270\272CSI\346\234\215\345\212\241\347\233\270\345\205\263\351\227\256\351\242\230/\345\220\257\345\212\250huawei-csi\346\234\215\345\212\241\346\227\266-\346\234\215\345\212\241\345\220\257\345\212\250\345\274\202\345\270\270-\347\212\266\346\200\201\346\230\276\347\244\272InvalidImageName.md" "b/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\215\216\344\270\272CSI\346\234\215\345\212\241\347\233\270\345\205\263\351\227\256\351\242\230/\345\220\257\345\212\250huawei-csi\346\234\215\345\212\241\346\227\266-\346\234\215\345\212\241\345\220\257\345\212\250\345\274\202\345\270\270-\347\212\266\346\200\201\346\230\276\347\244\272InvalidImageName.md" index 5db3d04..af19f05 100644 --- "a/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\215\216\344\270\272CSI\346\234\215\345\212\241\347\233\270\345\205\263\351\227\256\351\242\230/\345\220\257\345\212\250huawei-csi\346\234\215\345\212\241\346\227\266-\346\234\215\345\212\241\345\220\257\345\212\250\345\274\202\345\270\270-\347\212\266\346\200\201\346\230\276\347\244\272InvalidImageName.md" +++ "b/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\215\216\344\270\272CSI\346\234\215\345\212\241\347\233\270\345\205\263\351\227\256\351\242\230/\345\220\257\345\212\250huawei-csi\346\234\215\345\212\241\346\227\266-\346\234\215\345\212\241\345\220\257\345\212\250\345\274\202\345\270\270-\347\212\266\346\200\201\346\230\276\347\244\272InvalidImageName.md" @@ -40,7 +40,7 @@ controller和node的yaml配置文件中，配置Huawei CSI的镜像版本号错 kubectl edit daemonset huawei-csi-node -o yaml -n=huawei-csi ``` - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >- 示例yaml文件中huawei-csi-driver的参数image配置项，修改华为CSI镜像huawei-csi:4.5.0。 > ``` > containers: @@ -55,7 +55,7 @@ controller和node的yaml配置文件中，配置Huawei CSI的镜像版本号错 kubectl edit deployment huawei-csi-controller -o yaml -n=huawei-csi ``` - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >- 示例yaml文件中huawei-csi-driver的参数image配置项，修改华为CSI镜像huawei-csi:4.5.0。 > ``` > containers: diff --git "a/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\255\230\345\202\250\345\220\216\347\253\257\347\233\270\345\205\263\351\227\256\351\242\230/\344\275\277\347\224\250oceanctl\345\267\245\345\205\267\345\210\233\345\273\272\345\220\216\347\253\257\345\244\261\350\264\245-\346\212\245\351\224\231-context-deadline-exceeded.md" "b/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\255\230\345\202\250\345\220\216\347\253\257\347\233\270\345\205\263\351\227\256\351\242\230/\344\275\277\347\224\250oceanctl\345\267\245\345\205\267\345\210\233\345\273\272\345\220\216\347\253\257\345\244\261\350\264\245-\346\212\245\351\224\231-context-deadline-exceeded.md" index e94e001..1e95a5b 100644 --- "a/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\255\230\345\202\250\345\220\216\347\253\257\347\233\270\345\205\263\351\227\256\351\242\230/\344\275\277\347\224\250oceanctl\345\267\245\345\205\267\345\210\233\345\273\272\345\220\216\347\253\257\345\244\261\350\264\245-\346\212\245\351\224\231-context-deadline-exceeded.md" +++ "b/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\255\230\345\202\250\345\220\216\347\253\257\347\233\270\345\205\263\351\227\256\351\242\230/\344\275\277\347\224\250oceanctl\345\267\245\345\205\267\345\210\233\345\273\272\345\220\216\347\253\257\345\244\261\350\264\245-\346\212\245\351\224\231-context-deadline-exceeded.md" @@ -65,7 +65,7 @@ weight: 2 联系Kubernetes平台管理员查看kube-apiserver与CSI webhook网络问题。例如kube-apiserver存在HTTPS代理时可能无法访问CSI webhook服务。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >临时规避方案中，将会删除webhook资源，该资源用于在创建存储后端时校验输入的账户信息是否正确和能否和存储建立连接，因此删除该资源仅影响创建后端时的校验，无其他功能影响，但需要注意以下几点。 >- 请保证huawei-csi-controller服务所在宿主机能和存储通信。 >- 请保证输入的账号密码正确。 diff --git "a/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\255\230\345\202\250\345\220\216\347\253\257\347\233\270\345\205\263\351\227\256\351\242\230/\344\275\277\347\224\250oceanctl\345\267\245\345\205\267\347\256\241\347\220\206\345\220\216\347\253\257\346\227\266\350\260\203\347\224\250webhook\345\244\261\350\264\245.md" "b/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\255\230\345\202\250\345\220\216\347\253\257\347\233\270\345\205\263\351\227\256\351\242\230/\344\275\277\347\224\250oceanctl\345\267\245\345\205\267\347\256\241\347\220\206\345\220\216\347\253\257\346\227\266\350\260\203\347\224\250webhook\345\244\261\350\264\245.md" index e10a988..d913f14 100644 --- "a/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\255\230\345\202\250\345\220\216\347\253\257\347\233\270\345\205\263\351\227\256\351\242\230/\344\275\277\347\224\250oceanctl\345\267\245\345\205\267\347\256\241\347\220\206\345\220\216\347\253\257\346\227\266\350\260\203\347\224\250webhook\345\244\261\350\264\245.md" +++ "b/content/zh-cn/docs/\346\225\205\351\232\234\345\244\204\347\220\206/\345\255\230\345\202\250\345\220\216\347\253\257\347\233\270\345\205\263\351\227\256\351\242\230/\344\275\277\347\224\250oceanctl\345\267\245\345\205\267\347\256\241\347\220\206\345\220\216\347\253\257\346\227\266\350\260\203\347\224\250webhook\345\244\261\350\264\245.md" @@ -9,7 +9,7 @@ weight: 1 当webhook的配置发生改变后，例如修改webhookPort参数值后，此时使用oceanctl工具对后端进行管理时调用webhook报错，如下： -![](/figures/en-us_image_0000001524132062.png) +![](/css-docs/figures/en-us_image_0000001524132062.png) ## 根因分析{#zh-cn_topic_0000001279996521_section1425013451056} diff --git "a/content/zh-cn/docs/\346\246\202\350\277\260/_index.md" "b/content/zh-cn/docs/\346\246\202\350\277\260/_index.md" index cda59d9..db389fb 100644 --- "a/content/zh-cn/docs/\346\246\202\350\277\260/_index.md" +++ "b/content/zh-cn/docs/\346\246\202\350\277\260/_index.md" @@ -10,7 +10,7 @@ weight: 2 Kubernetes通过其官方维护的一系列sidecar组件负责注册监听Kubernetes对象资源，并在需要的时候通过gRPC发起对CSI Driver调用，华为CSI Driver将sidecar发起的调用在华为存储上实施，如创建一个[持久卷（Persistent Volume，PV）](https://kubernetes.io/docs/concepts/storage/persistent-volumes/)的操作被实施为在华为存储上创建一个LUN/文件系统。Kubernetes、华为CSI以及华为存储的整体结构如下图所示： **图 1** CSI整体架构 -![](/figures/CSI整体架构.png "CSI整体架构") +![](/css-docs/figures/CSI整体架构.png "CSI整体架构") 华为CSI主要有两大组件，分别为huawei-csi-controller和huawei-csi-node： @@ -20,7 +20,7 @@ Kubernetes通过其官方维护的一系列sidecar组件负责注册监听Kubern 华为CSI的部署模型如下所示： **图 2** CSI部署模型 -![](/figures/CSI部署模型.png "CSI部署模型") +![](/css-docs/figures/CSI部署模型.png "CSI部署模型") 本文档主要介绍华为CSI V4.5.0插件的安装部署和使用。 diff --git "a/content/zh-cn/docs/\351\231\204\345\275\225/\345\215\216\344\270\272CSI\350\265\204\346\272\220\347\256\241\347\220\206.md" "b/content/zh-cn/docs/\351\231\204\345\275\225/\345\215\216\344\270\272CSI\350\265\204\346\272\220\347\256\241\347\220\206.md" index c422f0e..0450e56 100644 --- "a/content/zh-cn/docs/\351\231\204\345\275\225/\345\215\216\344\270\272CSI\350\265\204\346\272\220\347\256\241\347\220\206.md" +++ "b/content/zh-cn/docs/\351\231\204\345\275\225/\345\215\216\344\270\272CSI\350\265\204\346\272\220\347\256\241\347\220\206.md" @@ -184,7 +184,7 @@ weight: 6 - Pod名称为huawei-csi-controller时，修改huawei-csi-controller.yaml文件。 - Pod名称为huawei-csi-node时，修改huawei-csi-node.yaml文件。 - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >Pod名称的分类，请参考[表 容器资源请求和限制](#table4106151116363)。 以修改Pod名称为huawei-csi-node中huawei-csi-driver容器的资源请求为例，执行命令编辑配置文件，找到spec.template.spec.containes.name为huawei-csi-driver的容器。按需修改资源请求和限制。 diff --git "a/content/zh-cn/docs/\351\231\204\345\275\225/\351\205\215\347\275\256\350\207\252\345\256\232\344\271\211\346\235\203\351\231\220.md" "b/content/zh-cn/docs/\351\231\204\345\275\225/\351\205\215\347\275\256\350\207\252\345\256\232\344\271\211\346\235\203\351\231\220.md" index 6455338..6ae1ba9 100644 --- "a/content/zh-cn/docs/\351\231\204\345\275\225/\351\205\215\347\275\256\350\207\252\345\256\232\344\271\211\346\235\203\351\231\220.md" +++ "b/content/zh-cn/docs/\351\231\204\345\275\225/\351\205\215\347\275\256\350\207\252\345\256\232\344\271\211\346\235\203\351\231\220.md" @@ -12,7 +12,7 @@ weight: 5 - NAS相关资源请参考[表 NAS相关资源最小权限说明](#table66121923174916)配置最小权限。 - SAN相关资源请参考[表 SAN相关资源最小权限说明](#table51362243359)配置最小权限。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >可参考存储文档：《[OceanStor Dorado 6000, Dorado 18000系列 产品文档](https://support.huawei.com/hedex/hdx.do?docid=EDOC1100214749&id=ZH-CN_TOPIC_0000001640708705)》配置自定义角色权限。 **表 1** NAS相关资源最小权限说明 diff --git "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\345\274\200\345\220\257PVC\345\217\230\346\233\264\347\211\271\346\200\247/\344\275\277\347\224\250Helm\345\274\200\345\220\257PVC\345\217\230\346\233\264\347\211\271\346\200\247.md" "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\345\274\200\345\220\257PVC\345\217\230\346\233\264\347\211\271\346\200\247/\344\275\277\347\224\250Helm\345\274\200\345\220\257PVC\345\217\230\346\233\264\347\211\271\346\200\247.md" index 8b81169..b266a7f 100644 --- "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\345\274\200\345\220\257PVC\345\217\230\346\233\264\347\211\271\346\200\247/\344\275\277\347\224\250Helm\345\274\200\345\220\257PVC\345\217\230\346\233\264\347\211\271\346\200\247.md" +++ "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\345\274\200\345\220\257PVC\345\217\230\346\233\264\347\211\271\346\200\247/\344\275\277\347\224\250Helm\345\274\200\345\220\257PVC\345\217\230\346\233\264\347\211\271\346\200\247.md" @@ -39,7 +39,7 @@ weight: 1 customresourcedefinition.apiextensions.k8s.io/volumemodifycontents.xuanwu.huawei.io configured ``` - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >如回显中存在“Warning: resource customresourcedefinitions/volumemodifycontents.xuanwu.huawei.io is missing the kubectl.kubernetes.io/last-applied-configuration...”提示，可忽略该提示。该提示出现原因是由于Helm安装应用时使用的是kubectl create命令而不是kubectl apply命令。 4. 执行以下命令，获取原有服务配置文件。 diff --git "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/_index.md" "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/_index.md" index d3c9858..541ffe8 100644 --- "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/_index.md" +++ "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/_index.md" @@ -41,7 +41,7 @@ PVC变更特性使用CRD实现，当前资源说明如下。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >- VolumeModifyClaim资源支持创建/删除/查询，不支持更新。 >- VolumeModifyContent资源仅支持查询，用于展示单个PVC变更详情，请勿手动创建/删除/修改。 >- VolumeModifyContent资源被VolumeModifyClaim管理，请勿手动管理VolumeModifyContent资源。 diff --git "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264/\345\207\206\345\244\207PVC\345\217\230\346\233\264\346\226\207\344\273\266.md" "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264/\345\207\206\345\244\207PVC\345\217\230\346\233\264\346\226\207\344\273\266.md" index 12eb49a..86ade50 100644 --- "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264/\345\207\206\345\244\207PVC\345\217\230\346\233\264\346\226\207\344\273\266.md" +++ "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264/\345\207\206\345\244\207PVC\345\217\230\346\233\264\346\226\207\344\273\266.md" @@ -108,7 +108,7 @@ PVC变更文件样例模板为/examples/volumemodifyclaim.yaml，具体配置项 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >- spec.source.kind和spec.source.name用于指定卷变更范围，例如配置为StorageClass和对应名称时，将会变更使用目标StorageClass发放的所有的处于Bound状态的PVC。 >- 当所有关联的PVC完成变更后，华为CSI会替换原有的StorageClass，并增加VolumeModifyClaim的spec.parameters参数，使得PVC满足StorageClass定义。 diff --git "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264\350\265\204\346\272\220.md" "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264\350\265\204\346\272\220.md" index 7658c20..0014b6b 100644 --- "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264\350\265\204\346\272\220.md" +++ "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264/\345\210\233\345\273\272PVC\345\217\230\346\233\264\350\265\204\346\272\220.md" @@ -7,7 +7,7 @@ weight: 2 本章节介绍如何基于已配置的PVC变更文件创建PVC变更资源。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >- 仅支持双活AA模式。 >- 如果变更场景为普通卷变更为双活卷，则仅支持变更主站点端存储卷。 >- 创建PVC变更资源期间，请勿使用华为CSI管理PVC。 diff --git "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\240\351\231\244PVC\345\217\230\346\233\264.md" "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\240\351\231\244PVC\345\217\230\346\233\264.md" index d774bc3..fe93847 100644 --- "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\240\351\231\244PVC\345\217\230\346\233\264.md" +++ "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\345\210\240\351\231\244PVC\345\217\230\346\233\264.md" @@ -5,7 +5,7 @@ description: weight: 3 --- ->![](/public_sys-resources/zh/icon-notice.gif) +>![](/css-docs/public_sys-resources/zh/icon-notice.gif) >- 当VolumeModifyClaim的STATUS值为Creating时，删除VolumeModifyClaim资源，将会在存储侧删除此次变更创建的资源，然后移除集群资源。在删除后，如果继续使用原有的StorageClass进行PVC管理，需要将关联的存储后端恢复为非双活存储后端。 >- 当VolumeModifyClaim的STATUS值为Pending或Completed时，删除VolumeModifyClaim资源，仅会移除集群资源，不会和存储交互，即不会在存储侧删除变更创建的资源。 >- VolumeModifyContent被VolumeModifyClaim管理，请勿手动管理VolumeModifyContent资源。 diff --git "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\346\237\245\350\257\242PVC\345\217\230\346\233\264.md" "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\346\237\245\350\257\242PVC\345\217\230\346\233\264.md" index 5fa34ea..09c8e6a 100644 --- "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\346\237\245\350\257\242PVC\345\217\230\346\233\264.md" +++ "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/PVC\345\217\230\346\233\264/\351\205\215\347\275\256PVC\345\217\230\346\233\264/\346\237\245\350\257\242PVC\345\217\230\346\233\264.md" @@ -78,7 +78,7 @@ weight: 2 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >VolumeModifyClaim支持使用kubectl查看Events信息，当VolumeModifyClaim无法满足创建要求，或者创建过程中出现错误时，服务端将记录Events信息。参考命令如下： >``` >kubectl describe volumemodifyclaims local-to-hypermetro @@ -150,7 +150,7 @@ VolumeModifyContent由VolumeModifyClaim资源创建，记录了单个PVC的变 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >VolumeModifyContent支持使用kubectl查看Events信息，当VolumeModifyContent无法满足创建要求，或者变更PVC出现错误时，服务端将记录Events信息。参考命令如下： >``` >kubectl describe volumemodifycontents myvmc-uid diff --git "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\200\232\350\277\207Helm\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\205\215\347\275\256\345\210\206\345\270\203\345\274\217\345\255\230\345\202\250\345\220\216\347\253\257\347\232\204ALUA\345\217\202\346\225\260.md" "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\200\232\350\277\207Helm\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\205\215\347\275\256\345\210\206\345\270\203\345\274\217\345\255\230\345\202\250\345\220\216\347\253\257\347\232\204ALUA\345\217\202\346\225\260.md" index 71d0688..1858c62 100644 --- "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\200\232\350\277\207Helm\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\205\215\347\275\256\345\210\206\345\270\203\345\274\217\345\255\230\345\202\250\345\220\216\347\253\257\347\232\204ALUA\345\217\202\346\225\260.md" +++ "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\200\232\350\277\207Helm\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\205\215\347\275\256\345\210\206\345\270\203\345\274\217\345\255\230\345\202\250\345\220\216\347\253\257\347\232\204ALUA\345\217\202\346\225\260.md" @@ -9,7 +9,7 @@ weight: 2 针对不同的操作系统，ALUA配置可能有所不同。进入[华为技术支持](https://support.huawei.com/enterprise/zh/index.html)，在搜索输入框中输入“主机连通性指南”，单击搜索。在搜索结果中，选择对应操作系统的主机连通性指南。结合实际需要根据指南的说明进行ALUA配置。华为CSI将在华为存储上对该主机的启动器应用您设置的配置项。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >已经发放的Pod的节点不会主动更改ALUA信息，需要通过在该节点重新发放Pod才会变更主机ALUA配置。 >分布式存储非双活场景，存储系统自身为Active/Active模式，选择“启用ALUA”没有实际意义，建议选择存储默认的“禁用ALUA”。因此不建议对分布式存储配置ALUA参数。 diff --git "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\200\232\350\277\207Helm\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\205\215\347\275\256\345\215\216\344\270\272\344\274\201\344\270\232\345\255\230\345\202\250\345\220\216\347\253\257\347\232\204ALUA\345\217\202\346\225\260.md" "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\200\232\350\277\207Helm\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\205\215\347\275\256\345\215\216\344\270\272\344\274\201\344\270\232\345\255\230\345\202\250\345\220\216\347\253\257\347\232\204ALUA\345\217\202\346\225\260.md" index 2045c26..e185285 100644 --- "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\200\232\350\277\207Helm\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\205\215\347\275\256\345\215\216\344\270\272\344\274\201\344\270\232\345\255\230\345\202\250\345\220\216\347\253\257\347\232\204ALUA\345\217\202\346\225\260.md" +++ "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\200\232\350\277\207Helm\351\205\215\347\275\256ALUA\347\211\271\346\200\247/\351\205\215\347\275\256\345\215\216\344\270\272\344\274\201\344\270\232\345\255\230\345\202\250\345\220\216\347\253\257\347\232\204ALUA\345\217\202\346\225\260.md" @@ -9,7 +9,7 @@ weight: 1 针对不同的操作系统，ALUA配置可能有所不同。进入[华为技术支持](https://support.huawei.com/enterprise/zh/index.html)，在搜索输入框中输入“主机连通性指南”，单击搜索。在搜索结果中，选择对应操作系统的主机连通性指南。结合实际需要根据指南的说明进行ALUA配置。华为CSI将在华为存储上对该主机的启动器应用您设置的配置项。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >已经发放的Pod的节点不会主动更改ALUA信息，需要通过在该节点重新发放Pod才会变更主机ALUA配置。 ## OceanStor V5系列和OceanStor Dorado V3系列存储后端的ALUA参数{#section16218353201717} @@ -102,7 +102,7 @@ parameters: 华为CSI支持的OceanStor和OceanStor Dorado系列存储的ALUA参数见[表 OceanStor和OceanStor Dorado系列存储的ALUA参数说明](#zh-cn_topic_0000001352783505_zh-cn_topic_0000001198982584_table7143850202411)。 ->![](/public_sys-resources/zh/icon-note.gif) +>![](/css-docs/public_sys-resources/zh/icon-note.gif) >OceanStor和OceanStor Dorado系列存储在默认情况下启动器主机访问模式即为“均衡模式”，因此不建议对OceanStor和OceanStor Dorado系列存储配置ALUA参数。 **表 2** OceanStor和OceanStor Dorado系列存储的ALUA参数说明 diff --git "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256\345\255\230\345\202\250\346\213\223\346\211\221\346\204\237\347\237\245/_index.md" "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256\345\255\230\345\202\250\346\213\223\346\211\221\346\204\237\347\237\245/_index.md" index 9cf32dd..06f0f48 100644 --- "a/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256\345\255\230\345\202\250\346\213\223\346\211\221\346\204\237\347\237\245/_index.md" +++ "b/content/zh-cn/docs/\351\253\230\347\272\247\347\211\271\346\200\247/\351\205\215\347\275\256\345\255\230\345\202\250\346\213\223\346\211\221\346\204\237\347\237\245/_index.md" @@ -63,7 +63,7 @@ weight: 2 - >![](/public_sys-resources/zh/icon-note.gif) + >![](/css-docs/public_sys-resources/zh/icon-note.gif) >- 拓扑标签必须以topology.kubernetes.io开头。拓扑标签示例： > - 示例1：topology.kubernetes.io/region=China-west > - 示例2：topology.kubernetes.io/zone=ChengDu