Alibaba Cloud Deployment Manual¶

1 Introduction¶

1.1 Document Overview¶

This document primarily covers the deployment on Alibaba 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 name example. Replace it with the appropriate domain during actual deployment.

1.2 Key Terms¶

1.3 Deployment Architecture¶

2 Resource Preparation¶

Alibaba Cloud Resource List

3 Infrastructure Deployment¶

3.1 Deployment Description¶

RDS, InfluxDB, OpenSearch, NAS Storage should be created according to the configuration requirements, all within the same region and under the same VPC network. ECS, SLB, NAT Gateway are automatically created by ACK, so there is no need to create them separately, meaning steps 1, 2, and 3 in the deployment diagram do not require separate creation.

3.2 Steps One, Two, Three - ACK Service Creation¶

3.2.1 Cluster Configuration¶

Enter Container Service for Kubernetes, create a Kubernetes cluster, select Managed Standard Cluster, and pay attention to the following cluster configuration requirements:

• It must be in the same region as the previously created RDS, InfluxDB, Elasticsearch, etc.
• Select the "Configure SNAT" option (ACK will automatically create and configure the NAT Gateway to enable outbound internet access for the cluster)
• Select the "Public Access" option (to allow public access to the cluster API; if you are managing the cluster internally, this can be unchecked)
• Choose flexvolume as the storage driver temporarily when enabling ACK services; CSI drivers are not supported in this document yet.

3.2.2 Worker Configuration¶

Mainly choose the ECS specifications and quantity. Specifications can be selected based on the configuration list or assessed according to actual needs, but they must not fall below the minimum requirements. There should be at least 3 nodes, or more.

3.2.3 Component Configuration¶

Component configuration must include selecting the "Install Ingress Component" option, choosing "Public" type. ACK will automatically create a public SLB. After installation, point the domain to the public IP of this SLB.

3.3 Steps Four, Five - Dynamic Storage Configuration¶

Create the NAS file system in advance and obtain the nas_server_url.

3.3.1 Dynamic Storage Installation¶

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: alicloud-nas
mountOptions:
- nolock,tcp,noresvport
- vers=3
parameters:
  volumeAs: subpath
  server: "{{ nas_server_url }}:/k8s/"
provisioner: nasplugin.csi.alibabacloud.com
reclaimPolicy: Retain

kubectl apply -f ./alicloud-nas-subpath.yaml

kubectl apply -f nas_controller.yaml

kubectl get pod -nkube-system | grep alicloud-nas-controller

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: alicloud-nas
  annotations:
    storageclass.beta.kubernetes.io/is-default-class: "true"
    storageclass.kubernetes.io/is-default-class: "true"
mountOptions:
- nolock,tcp,noresvport
- vers=3
parameters:
  server:  "{{ nas_server_url }}:/k8s/"
  driver: flexvolume
provisioner: alicloud/nas
reclaimPolicy: Delete

kubectl apply -f ./storage_class.yaml

3.3.2 Verification of Deployment¶

3.3.2.1 Create PVC and Check Status¶

Run the command to create a PVC:

$ cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
 name: cfs-pvc001
spec:
 accessModes:
   - ReadWriteOnce
 resources:
   requests:
     storage: 1Gi
 storageClassName: alicloud-nas
EOF

3.3.2.2 Check PVC¶

$ kubectl get pvc | grep cfs-pvc001

cfs-pvc001       Bound    pvc-a17a0e50-04d2-4ee0-908d-bacd8d53aaa4   1Gi        RWO            alicloud-nas           3d7h

Bound indicates successful deployment.

3.4 Step Six - Cache Service¶

• You can use the default built-in cache service.
• If you do not use the default built-in cache service, configure Redis as follows:
• Redis Version: 6.0, supporting standalone mode, proxy mode, and master-slave mode Redis clusters.
• Configure Redis password.
• Add the automatically created ECS internal IP to the Redis whitelist.

3.5 Step Seven - InfluxDB¶

• Create an administrator account (must be an administrator account, required for subsequent initialization and DB/RP creation).
• Add the internal IP of the ECS instances automatically created by ACK to the InfluxDB whitelist.

3.6 Step Eight - OpenSearch¶

• Create an administrator account.
• Install the Chinese segmentation plugin.
• Add the internal IP of the ECS instances automatically created by ACK to the OpenSearch whitelist.

3.7 Step Nine - RDS¶

• Create an administrator account (must be an administrator account, required for subsequent initialization and creation of various application DBs).
• Modify parameter configurations in the console to set innodb_large_prefix to ON.
• Add the internal IP of the ECS instances automatically created by ACK to the RDS whitelist.

4 kubectl Installation and Configuration¶

4.1 Install kubectl¶

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

https://kubernetes.io/docs/tasks/tools/install-kubectl/

4.2 Configure kube config¶

For kubectl to manage the cluster, the cluster's kubeconfig content must be placed in the $HOME/.kube/config file. You can find the kubeconfig content in the cluster's Basic Information section.

Choose whether to use the public or private kubeconfig based on whether your operations machine is connected to the cluster's internal network.

5 Start Installation¶

After completing the above operations, refer to the manual Start Installation for further instructions.