Huawei Cloud Deployment Manual

1 Introduction¶

1.1 Document Description¶

This document primarily describes the deployment on Huawei Cloud, introducing the complete steps from resource planning and configuration to deploying Guance and running it.

Note:

• This document uses dataflux.cn as the primary domain for examples. Replace it with the corresponding domain during actual deployment.

1.2 Key Terms¶

1.3 Deployment Architecture¶

2 Resource List¶

3 Infrastructure Deployment¶

3.1 Deployment Instructions¶

RDS, Redis, InfluxDB, Elasticsearch should be created according to the configuration requirements, all within the same VPC network in the same region.

3.2 Steps One, Two, Three: CCE Service Creation¶

3.2.1 Step One: Purchase CCE Cluster¶

Go to the official website, select Products in the navigation bar, choose Container, click Cloud Container Engine CCE, and create a CCE cluster.

• It must be in the same region as the RDS, InfluxDB, Elasticsearch resources created later.
• Choose the cluster size based on your needs; you will then create worker nodes afterward.

3.2.2 Step Two: Worker Node Configuration¶

Primarily choose ECS specifications and quantity. Specifications can be created according to the resource list or assessed based on actual conditions but must not be lower than the minimum configuration requirements. There should be at least 3 nodes or more, and it is recommended that the data disk size should not be less than 100GiB.

3.2.3 Step Three: Plugin Management¶

Everest and coredns plugins are created by default when purchasing a k8s cluster. It is recommended to add the following two plugins. To ensure cluster resources and avoid additional costs, it is suggested to remove the ICAgent plugin.

Install nginx-ingress plugin

1) Configure CPU and memory resource limits

2) Create Load Balancer ELB

If needed, you can choose a dedicated elastic load balancer. This document chooses the shared type. Note: Select an elastic public IP and it is recommended to use an existing one or create a new one with a bandwidth of 300Mbit/s charged by traffic.

• Differences between dedicated and shared types can be found at the following link:

https://support.huaweicloud.com/productdesc-elb/elb_pro_0004.html

3) Configure nginx-ingress plugin content related to nginx forwarding

# Add the following content
{
    "allow-backend-server-header": "true",
    "client-header-buffer-size": "32k",
    "enable-underscores-in-headers": "true",
    "forwarded-for-header": "X-Forwarded-For",
    "generate-request-id": "true",
    "ignore-invalid-headers": "true",
    "keep-alive-requests": "100",
    "large-client-header-buffers": "4 32k",
    "proxy-body-size": "20m",
    "proxy-connect-timeout": "20",
    "reuse-port": "true",
    "server-tokens": "false",
    "ssl-protocols": "TLSv1 TLSv1.1 TLSv1.2 SSLv3",
    "ssl-redirect": "false",
    "use-gzip": "true",
    "worker-cpu-affinity": "auto"
}

Install node-local-dns plugin

• Enable DNS Config injection functionality

Uninstall ICAgent plugin (optional)

Select AOM Application Operation Management and uninstall the ICAgent plugin, and turn off the switches for continuing to collect logs and metrics beyond the quota.

3.4 Step Four: Cache Service¶

• You can choose to use the default built-in cache service. If not using the default built-in cache service, configure Redis according to the following requirements:
• Distributed caching service (Redis version).
• Redis version: 6.0, standard master-slave architecture, supporting dual replicas.
• Set a Redis password.
• Add the internal network IP addresses of ECS instances automatically created by CCE to the Redis whitelist.

3.5 Step Five: InfluxDB¶

• Name: Cloud Database GaussDB(for influx)
• Version: 1.7
• Set InfluxDB user password
• Add the internal network IP addresses of ECS instances automatically created by CCE to the InfluxDB whitelist

3.6 Step Six: Elasticsearch¶

• Name: Cloud Search Service CSS
• Version: 7.10.2
• Enable security mode to set up admin accounts and passwords
• Add the internal network IP addresses of ECS instances automatically created by CCE to the Elasticsearch whitelist

3.7 Step Seven: RDS¶

• Name: Cloud Database RDS
• Version: 8.0, standard master-slave edition
• Set MySQL root user password
• Add the internal network IP addresses of ECS instances automatically created by CCE to the MySQL whitelist

4 kubectl Installation and Configuration¶

4.1 Install kubectl¶

kubectl is a command-line client tool for Kubernetes, which can be used to deploy applications, check and manage cluster resources, etc. Our Launcher is based on this command-line tool for deploying applications. Refer to the official documentation for specific installation methods:

Install and configure kubectl

You can also click on the cluster and find kubectl Click to View

4.2 Configure kube config¶

Choose whether to use the public or private network kubeconfig based on whether your operations machine can connect to the cluster's internal network. Determine the connection method based on the following use cases.

5 Start Installation¶

After completing the operations, refer to the manual Start Installation