Overview
AutoMQ Cloud BYOC environments support deployment to managed Kubernetes platforms provided by major cloud providers such as AWS EKS, GCP GKE, Alibaba Cloud ACK, and Huawei Cloud CCE. This article introduces the basic concepts, architecture, and constraints of deploying AutoMQ to Kubernetes platforms.
In this article, references to AutoMQ product service provider, AutoMQ service provider, and AutoMQ all specifically refer to AutoMQ HK Limited and its affiliates.
Deployment Architecture
The architecture for deploying AutoMQ Cloud BYOC environments to Kubernetes is as follows:
Note:
In the AutoMQ BYOC environment, the console component is still deployed outside the Kubernetes cluster, typically using a cloud provider's virtual machine. Deployment and installation are carried out by obtaining management permission Config for the Kubernetes cluster.
Users manage the lifecycle of instances within the environment via the WebUI provided by the AutoMQ console or the Terraform Provider.
AutoMQ data plane instances (clusters) are deployed to the Kubernetes cluster designated by the user.
Each environment can support multiple instances simultaneously and allow the deployment of multiple instances across different Kubernetes clusters (under development; currently, only 1 Kubernetes cluster is supported).
Constraints and Limitations
When deploying AutoMQ on Kubernetes, users need to follow the constraints and limitations outlined below. Improper user operations may lead to deployment and modification failures of the cluster.
Constraint 1: Users Must Provide a Dedicated Kubernetes Cluster that Meets the Requirements
AutoMQ requires a dedicated Kubernetes cluster that should not be shared with other application systems for the following reasons:
Network isolation risk in Kubernetes: AutoMQ is designed for high-throughput data transmission scenarios and demands high network throughput. Network isolation between different Pods within a Kubernetes cluster is not complete. AutoMQ requires an independent Kubernetes cluster to avoid interference with other business systems of the user.
Operations authorization isolation: The Kubernetes cluster where AutoMQ resides needs to provide operations authorization (granting AutoMQ service provider access to the cluster). AutoMQ requires an independent Kubernetes cluster to prevent unauthorized access by application systems.
Multiple AutoMQ instances (clusters) can be deployed within the Kubernetes cluster. It is generally recommended that Kubernetes clusters are shared among the same business lines under the same VPC.
Constraint 2: Users Are Required to Create Node Pools, Provide Compliant Machine Types, and Ensure Node Supply as Specified
AutoMQ requires users to create node pools according to specifications. When creating instances in the AutoMQ console, it checks whether the node pools provided by the user meet the requirements. The specific requirements are as follows:
- Compliant Machine Types: AutoMQ selects corresponding network-optimized virtual machine instances from different cloud providers to offer the best cluster performance. When creating node pools, users must select compliant machine types. Refer to the table below for specific machine information:
| Cloud Provider | Allowed Machine Types List |
|---|---|
| Google Cloud | Small Machine Types:
|
| Huawei Cloud | Small Machine Types:
Large Machine Types:
|
Node Pool Role Authorization Requirements: AutoMQ clusters need to access services such as object storage and EBS during operation. Therefore, users must grant appropriate roles and permissions to the node pools and ensure that these authorizations are not modified or revoked.
Zone (Subnet) Requirements: AutoMQ supports both single-zone and three-zone instances. Hence, users need to create corresponding node pools for single-zone and three-zone instances, and they cannot be mixed.
For example: Users need to create three AutoMQ instances, namely instance1 (Zone A), instance2 (Zone B), and instance3 (Zone A, B, C). Therefore, users need to create three node pools, selecting Zone A, Zone B, and Zone A+B+C, respectively.