Mounting an OBS Bucket in an Edge AZ to a Remote CCE Turbo Cluster

Prerequisites

• A remote CCE Turbo cluster is available. It has some nodes in edge AZs. For details, see Using Distributed Cloud Resources in a CCE Turbo Cluster.
• The cluster has the CCE Container Storage (Everest) 2.4.111 or later installed in it.

Procedure

1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
2. Create a PVC in the cluster and dynamically create an OBS bucket in an edge AZ. The file content is as follows:

   apiVersion: v1
   kind: PersistentVolumeClaim
   metadata:
     name: obs-0001
     namespace: default
     annotations:
       everest.io/obs-volume-type: STANDARD
       csi.storage.k8s.io/fstype: s3fs
       csi.storage.k8s.io/node-publish-secret-name: for-obs-cloudpond  # Name of an OBS access key
       csi.storage.k8s.io/node-publish-secret-namespace: default # Namespace where an OBS access key is in
       everest.io/enterprise-project-id: '0' # Enterprise project ID
       everest.io/csi.obs-ies-location: *****  # ID of an OBS edge AZ, which should be confirmed with the Huawei Cloud OBS support personnel
   spec:
     accessModes:
       - ReadWriteMany
     resources:
       requests:
         storage: 1Gi
     storageClassName: csi-obs

3. Create a VPC endpoint to enable the networking between the OBS bucket in the edge and the edge node.
   1. Log in to API Explorer.
   2. Configure APIs and switch to text input in the Body parameter.

      

      The text format is as follows:

      {
        "vpc_id": "*****",
        "subnet_id": "*****",
        "endpoint_service_id": "*****"
      }

      • vpc_id: ID of the VPC to which a cluster belongs
      • subnet_id: ID of the subnet to which an edge node belongs
      • endpoint_service_id: ID of the OBS endpoint service, which should be confirmed with the Huawei Cloud OBS support personnel

4. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Workloads. In the right pane, click Create Workload in the upper right corner.
5. Configure the key parameters as shown below. Configure other parameters as required. For details about how to create a workload, see Creating a Deployment.
   1. In the Container Settings area, click Data Storage, click Add Volume, choose PVC from the drop-down list, and select the previously created PVC.

      

   2. In the Advanced Settings area, click Scheduling and set Node Affinity to Specify node or Specify node pool to ensure that the pod can be scheduled to the expected edge node. You can also customize the scheduling policy as required. For details, see Configuring Node Affinity Scheduling (nodeAffinity).

      

   3. In the Advanced Settings area, click Toleration and add a toleration based on the default taint on the edge node. The taint key and value are as follows:
      • Taint key: distribution.io/category
      • Operator: Equal
      • Taint value: IES

      

6. Click Create Workload.