Tenant Clusters Are Self-Built Clusters

2025-07-17 06:26:01

Precautions

  • The cluster component mounts the /data (non-crio) and /root (crio) directories of the k8s node host during runtime. Make sure the privileges of the directories are correct.

  • Make sure your k8s cluster allows outbound policy TCP ports: 31080, 30432, and 32345.

Obtaining Deployment Scripts

1.         Go to the CSG Console.

2.         Select Installation configuration > Component installation on the left navigation bar to go to the Component installation page.

3.         Click "Deployment script" to go to the deployment script page.

4.         The cluster name is automatically generated by the system and cannot be changed.

5.         Download images.

        a.          Select the container running environment (supporting docker, containerd, and CRI-O).

        b.         Select the cluster CPU architecture (supporting X86 and ARM architectures).

        c.         Click"Download Image Tar Package" to download the image Tar package locally and then load it 

into your private repository (please do not change the image name).

The Tar package has four images, as follows:

  • library/dosec-agent:2024-03-06T18.58.08V5.2.0_release_1e1cc2_f1e038c378,library

  • dosec-host-tool:alpineV3.8,library

  • dosec-scanner:2024-04-22T19.37.51V5.2.0_release_c60e9b_93f9a30a7b,library

  • dosec-server:2024-04-22T21.23.54V5.2.0_release_4933b2_523a6375b4

6.         Generate deployment scripts.

        a.          Select eSurfing Cloud VPC and VPC subnet, and enter the address, account number, 

and password of the private repository.

        b.          Click"Generate yaml file"and save the yaml file locally.

Installing and Deployment

After successfully downloading the kubectl.yaml file, perform the following steps to automatically finish the deployment:

1.         Log on to the cluster K8S Master node.

2.         Execute the kubectl apply-f kubectl.yaml command.

Successful Deployment

  • Go to Installation configuration > Component status  to see the specific deployment situation.

  • After the deployment is successful, the server reports the tenant information to the database and displays it associated with the project information.


NMWc0AvPXhPk