Use CloudBox in an ACK dedicated cluster

Updated at:

CloudBox is a fully managed, integrated hardware and software solution that extends Alibaba Cloud's public cloud infrastructure (compute, storage, and network resources) to your on-premises data center. It meets business requirements for data security, local data processing, and low latency. An ACK dedicated cluster can use resources from a CloudBox through a CloudBox node pool.

Important

To use CloudBox resources in an ACK dedicated cluster, submit a ticket to apply for permission to create new ACK dedicated clusters.

Prerequisites

  • You have created a CloudBox, purchased resources, and completed CloudBox acceptance, and the CloudBox is in the Running state. For more information, see Purchase a CloudBox. For details about the billing and specifications of compute resources, see Compute SKU specifications.

  • You have established a reliable, low-latency, and highly available network connection between your CloudBox and the public cloud region. To ensure a smooth user experience, a minimum bandwidth of 50 Mbps is recommended. For specific requirements, see Deployment requirements.

  • You have created a vSwitch in the CloudBox zone. For more information, see Create and manage vSwitches.

Limitations

Limitation

Description

Region

The ACK dedicated cluster that uses CloudBox resources must be in the same region as the CloudBox.

Basic networking

  • You cannot create Application Load Balancer (ALB) instances or Internet NAT gateways in a CloudBox zone. However, you can create Internet NAT gateways in a public cloud zone.

  • You cannot associate an elastic IP address (EIP) with Pods, Server Load Balancer (SLB) instances, or worker nodes in the CloudBox.

Cluster network mode

Only ACK dedicated clusters that use the Flannel network plugin can use CloudBox resources. The Terway network plugin is not supported.

Service

  • When you create a LoadBalancer-type Service in a CloudBox, you must specify the corresponding zone. For more information, see Add annotations to the YAML file of a Service to configure CLB instances.

  • A LoadBalancer-type Service in a CloudBox can only be associated with ECS instances within that same CloudBox. A similar Service in the public cloud can only be associated with ECS instances in the public cloud.

Nodes and node pools

  • You cannot create worker nodes with encrypted disks or use preemptible instances as worker nodes in a CloudBox zone.

  • If you enable autoscaling for a node pool that uses CloudBox resources, policies related to preemptible instances are not supported.

Usage notes

When the network connection between the CloudBox and the public cloud is interrupted, existing CloudBox ECS instance nodes in the cluster continue to run. However, you cannot manage workloads running on nodes in the CloudBox or add new CloudBox ECS instances to the cluster. Check the CloudBox network and restore the connection as soon as possible.

Procedure

To use resources from your CloudBox, create a CloudBox node pool in your ACK dedicated cluster. Follow these steps to create a control plane and a node pool in the CloudBox zone.

  1. Log on to the ACK console. In the left navigation pane, click Clusters.

  2. On the Clusters page, click Create Kubernetes Cluster.

  3. Click the ACK Dedicated Cluster tab, configure the key parameters listed in the following table, and then follow the on-screen instructions to create the cluster.

    The following table describes only the key parameters required to use CloudBox resources. For a detailed description of all parameters, see Create an ACK dedicated cluster (discontinued).

    Parameter

    Description

    Region

    Select the region where your CloudBox is deployed.

    Configure SNAT for VPC

    Clear the Configure SNAT for VPC checkbox.

    vSwitch

    Select a vSwitch in the CloudBox zone.

    Expose API server with EIP

    Clear the Expose API server with EIP checkbox.

    Network Plug-in

    Select Flannel.

    Once created, you can view the cluster on the Clusters page of the Container Service for Kubernetes console.