Huawei Cloud Deployment Manual

1 Prerequisites¶

1.1 Document Description¶

This document mainly introduces the complete steps from resource planning and configuration to deployment of Guance, using Huawei Cloud as an example.

Note:

• This document uses dataflux.cn as the main domain name example. In actual deployment, replace it with the corresponding domain name.

1.2 Keywords¶

1.3 Deployment Architecture¶

2 Resource List¶

3 Infrastructure Deployment¶

3.1 Deployment Notes¶

Create RDS, Redis, Elasticsearch according to the configuration requirements and deploy them within the same region under the same VPC network.

3.2 Step One, Two, Three: Create CCE Service¶

3.2.1 Step One: Purchase a CCE Cluster¶

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

• Must be in the same region as the RDS, ECS, and other resources created later
• Select the cluster scale based on your own situation, as this determines how many worker nodes will be created.

3.2.2 Step Two: Worker Node Configuration¶

Mainly select the ECS specifications and quantity. Specifications can be created according to the configuration list or evaluated based on actual conditions, but must not be lower than the minimum configuration requirements. At least 3 or more worker nodes should be deployed. It is recommended that the data disk size should not be less than 100GiB.

3.2.3 Step Three: Plugin Management¶

The everest and coredns plugins have already been created by default when purchasing the k8s cluster. It is recommended to add the following two plugins here. Also, to ensure cluster resources and avoid additional costs, it is recommended to delete the ICAgent plugin.

Install nginx-ingress plugin

1) Configure CPU and memory resource limits

2) Create Load Balancer ELB

You can choose a dedicated elastic load balancer if needed. This article selects the shared type. Note: When selecting an Elastic Public IP, it is recommended to use an existing one or create a new one with a bandwidth of 300Mbit/s billed by traffic.

• Differences between dedicated and shared types:

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

3) Configure nginx-ingress plugin regarding nginx forwarding content

# 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 Feature

Delete ICAgent plugin (optional)

Select AOM Application Operations Management and uninstall the ICAgent plugin, and turn off the switches for continuing log collection beyond quota and metric collection.

3.4 Step Four: Cache Services¶

• You can choose to use the built-in cache service by default. If you do not use the built-in cache service, configure Redis according to the following requirements:
• Distributed Cache Service (Redis version).
• Redis version: 6.0, standard master-slave architecture, supports dual replicas.
• Configure Redis password.
• Add the internal IP addresses of the ECS instances automatically created by CCE to the Redis whitelist.

3.5 Step Five: GuanceDB for Metrics¶

Installation Guide

3.6 Step Six: Elasticsearch¶

• Name: Cloud Search Service (CSS)
• Version: 7.10.2
• Enable secure mode to set administrator account and password
• Add the internal IP addresses of the 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 IP addresses of the ECS instances automatically created by CCE to the MySQL whitelist

4 Install and Configure kubectl¶

4.1 Install kubectl¶

kubectl is a command-line client tool for Kubernetes, which allows you to deploy applications, inspect and manage cluster resources. Our Launcher is based on this command-line tool to deploy applications. For specific installation methods, please refer to the official documentation:

Install and Configure kubectl

Alternatively, click on the cluster and find kubectl View Details.

4.2 Configure kube config¶

Whether to use public access or private access kubeconfig depends on whether your operations machine can connect to the cluster via the internal network. Determine the access method based on the Use Cases below:

5 Start Installation¶

After completing the above operations, refer to the manual Start Installation