Skip to Main Content

Deploy to HuaWei Cloud CCE

Refer to Overview▸, AutoMQ supports deployment on Kubernetes. This article describes the installation process of deploying AutoMQ on the Huawei Cloud CCE platform.

In this article, AutoMQ Product Service Provider, AutoMQ Service Provider, and AutoMQ specifically refer to AutoMQ HK Limited and its subsidiaries.

Procedure​

Step 1: Install Environment Console​

Refer to Overview▸, AutoMQ supports deployment on CCE clusters. In the CCE deployment mode, it is still necessary to install the AutoMQ console first, and then manage the CCE through the console interface to deploy the cluster to CCE.

On Huawei Cloud, both cloud marketplace and Terraform-based installations of the environment console are supported.

Note:

When installing the environment console as described above, the cluster deployment type must be set to Kubernetes for Install Env via Huawei Marketplace▸. This ensures support for subsequent steps 2-4, installing the AutoMQ cluster on CCE.

After the AutoMQ console installation is complete, you need to obtain the environment console address, initial username, password, and permission delegation required by AutoMQ from the console interface or Terraform output menu. This delegation will be used in step 1 to create the CCE node pool.

Step 2: Create CCE Cluster​

Refer to Overview▸, users need to create an independent CCE cluster in advance for AutoMQ utilization. Users can follow the steps outlined on the Huawei Cloud CCE product console.

  1. Log in to the Huawei Cloud CCE Console. Click Purchase Cluster.
  1. Select the cluster type as CCE Turbo and choose the billing mode and version according to the recommendations. It is recommended to choose a cluster size of 200-1000 nodes.

The network configuration needs to be set according to the following requirements:

  • Node subnet: Select a subnet with a sufficient IP range, recommended not less than /20, to avoid the inability to create machines later.

  • Container subnet and service subnet: Similarly, choose a subnet with sufficient IPs, recommended not less than /20, to avoid the inability to create Pods later.

  • Service forwarding mode: Make sure to select the IPVS mode.

Note:

When creating a CCE cluster, it is recommended to deselect the "Observability and local domain name resolution acceleration plugins". This is to avoid excessive consumption of node resources that may cause elastic scaling anomalies.

  1. Click on Create Cluster and wait a few minutes for the creation to complete.

  2. Once the cluster is created, go to the cluster details, Plugin Center, and install the CCE Cluster Elastic Engine Plugin.

Note:

During the elastic plugin deployment, select "Small Scale". This prevents the elastic scaling components of CCE from occupying too many node resources, which could lead to installation failure.

  1. Go to the cluster's Configuration Center, Network Configuration Tab, and enable Pod Access Metadata. Confirm and submit.
  1. Go to the cluster's Configuration Center, Cluster Auto-scaling Tab, enable Elastic Shrinkage, and check Ignore CPU and Memory Pre-allocation for DaemonSet Containers. Confirm and submit.

Step 3: Create a Public Node Pool for the CCE Cluster​

Refer to Overview▸, users need to create a public node pool for CCE system components deployment. Follow the steps below to create the node pool that meets the requirements.

  1. Enter the CCE cluster details created in Step 1, click the Node Management menu, and Create Node Pool. It is recommended to select at least 2 nodes with 4c8G models for deploying the CCE system components.

Step 4: Create a Dedicated CCE Node Pool for AutoMQ and Grant Delegated Authorization​

Refer to Overview▸, users need to create a dedicated node pool for AutoMQ to apply for machine instances for subsequent deployment. Follow the steps below to create the node pool that meets the requirements and complete the delegation authorization.

  1. Go to the CCE cluster details created in Step 1, click on the Node Management Menu, and Create Node Pool.
  1. Refer to the following documentation to set custom parameters and complete the node pool creation. For parameters not specified in the table, please use the default recommended values.

When creating a node pool, only single availability zone or three availability zones are supported. If a different number of availability zones is selected, instances cannot be created later.

Parameter Settings
Value Description
Node Pool Name
  • Description: Enter a distinguishable name according to the business semantics.
Node Type
  • Description: Specify the node pool model. Please refer to the document Overview▸ for model details.

Note: AutoMQ must run on the specified VM model. If a non-preset model is selected for the node pool creation, it cannot be used subsequently.

Availability Zone
  • Description: Choose one or three availability zones based on the actual needs of the AutoMQ cluster.

Note:
AutoMQ requires the availability zones for subsequent cluster creation to be completely consistent with the node pool. Therefore, if a single availability zone AutoMQ cluster is needed, create a single availability zone node pool here; if a three availability zone AutoMQ cluster is needed, create a three availability zone node pool here. Mixing the two is not allowed.

Entrusted Name
  • Description: The AutoMQ cluster needs to access cloud services such as OBS and network; therefore, the node pool needs authorization for these operations. During Step 1, when installing the BYOC environment, the corresponding entrustment is created. Select to bind this entrustment when creating the node pool. Deploy to Huawei Cloud CCE▸
Taint
  • Description: To prevent other workloads in the Kubernetes cluster from occupying the resources of the dedicated AutoMQ nodes, taints need to be applied to the dedicated AutoMQ node pool.
  • The taint key is dedicated, the value is automq, and the effect is NO_SCHEDULE.
  1. Bind the entrusted information to the node pool; the entrusted information comes from Step 1 Deploy to Huawei Cloud CCE▸ installation console output parameters. Also, add a taint to the node pool, the key of the taint is dedicated, the value is automq, and the effect is NO_SCHEDULE.
  1. After the node pool is created, click on Elastic Scaling and enable the elastic scaling rules for the specified availability zone.

When setting the elastic scaling rules for the node pool, ensure the following two configurations are correct:

Number of nodes range: It is recommended to retain at least 1 node. The range should be reasonably assessed based on the subsequent AutoMQ cluster scale. If the setting is too small, it will result in insufficient nodes for deployment.

Specification selection: Make sure to enable all machine types that meet the conditions in all available zones.

  1. Click the scaling menu of the node pool to scale the initial node capacity. It is recommended to scale 1 node per availability zone.

Step 5: Enter the Environment Console and Configure the Kubernetes Cluster Information.​

When entering the AutoMQ BYOC console for the first time, you need to configure the Kubernetes cluster information and Kubeconfig to use it normally. Follow the console's guidance page to fill in the CCE cluster ID and Kubeconfig created in Step 2 to complete the environment initialization.

  1. Copy the cluster ID of the GKE cluster created in Step 2.
  1. Find the Kubectl configuration menu and obtain the Kubeconfig configuration file.

Click on Kubectl configuration, set it to intranet access, and download the Kubeconfig configuration file.

Log in to the console, enter the cluster ID and Kubeconfig, and complete the initialization.