CloudBox is a fully managed cloud service that integrates Alibaba Cloud public cloud hardware and software—computing, storage, and network—directly into your on-premises data center, addressing business requirements including data security, on-premises data processing, and low latency. ACK dedicated clusters support CloudBox node pools to utilize resources deployed in the CloudBox.
To use CloudBox resources in an ACK dedicated cluster, submit a ticket to request permission to create an ACK dedicated cluster.
Prerequisites
Before you begin, ensure that you have:
-
A CloudBox that is created, resources are purchased, CloudBox acceptance is completed, and the CloudBox operates normally. For billing and compute SKU specifications, see Compute SKU specifications.
-
A highly available, low-latency connection between the CloudBox and the public cloud. For reliable performance, use a connection with 50 Mbit/s bandwidth or higher. For connection requirements, see Deployment requirements.
-
A vSwitch created in the CloudBox zone. See Create and manage vSwitches.
Limitations
Region
The ACK dedicated cluster and the CloudBox must be in the same region.
Network
-
You cannot create Application Load Balancer (ALB) instances or Internet NAT gateways in the CloudBox zone. Create Internet NAT gateways in a public cloud zone instead.
-
You cannot associate elastic IP addresses (EIPs) with pods, Server Load Balancer (SLB) instances, or worker nodes deployed in the CloudBox.
Network plugin
Only ACK dedicated clusters using the Flannel network plugin support CloudBox resources. Clusters using the Terway network plugin do not support CloudBox resources.
LoadBalancer-type services
-
When creating a LoadBalancer-type Service in the CloudBox, specify the CloudBox zone for the Service. See Add annotations to the YAML file of a Service to configure CLB instances.
-
A LoadBalancer-type Service in the CloudBox can only be associated with ECS instances in the same CloudBox. A LoadBalancer-type Service in the public cloud can only be associated with ECS instances on the public cloud.
Nodes and node pools
-
You cannot use ECS instances with encrypted disks or preemptible instances as worker nodes in the CloudBox zone.
-
Node pools with CloudBox resources and autoscaling enabled do not support preemptible instance policies.
Network disconnection behavior
When the connection between the CloudBox and the public cloud is interrupted, existing ECS nodes in the ACK cluster continue to run normally. However, you cannot manage workloads on those nodes or add new ECS nodes from the CloudBox to the cluster. Check the CloudBox network and restore the connection as soon as possible.
Create a CloudBox node pool in an ACK dedicated cluster
-
Log on to the ACK console. In the left navigation pane, click Clusters.
-
On the Clusters page, click Create Kubernetes Cluster.
-
Click the ACK Dedicated Cluster tab. Configure the following key parameters, then follow the on-screen instructions to create the cluster. The table below describes parameters specific to CloudBox deployments. For all parameter descriptions, see Create an ACK dedicated cluster (discontinued). After the cluster is created, it appears on the Clusters page in the Container Service for Kubernetes console.
Parameter Value Region Select the region of the CloudBox Configure SNAT for VPC Clear the checkbox vSwitch Select a vSwitch in the CloudBox zone Expose API server with EIP Clear the checkbox Network Plug-in Select Flannel