This topic describes how to create an ACK dedicated cluster for heterogeneous computing in the Container Service for Kubernetes (ACK) console.

Background information

ACK performs the following operations when a cluster is created:

  • Creates ECS instances, configures a public key to enable SSH logon from master nodes to other nodes, and then configures the ACK cluster through CloudInit.
  • Creates a security group that allows access to the VPC over Internet Control Message Protocol (ICMP).
  • If you do not specify an existing VPC, ACK creates a VPC and a vSwitch and creates SNAT entries for the vSwitch.
  • Adds route entries to the VPC.
  • Creates a NAT gateway and EIPs.
  • Creates a Resource Access Management (RAM) user and an AccessKey pair. Grants the following permissions to the RAM user: permissions to query, create, and delete ECS instances, permissions to add and delete disks, and full permissions on SLB, CloudMonitor, VPC, Log Service, and Apsara File Storage NAS (NAS). The ACK cluster automatically creates SLB instances, disks, and VPC route entries based on your configuration.
  • Creates an internal-facing SLB instance and opens port 6443.
  • Creates an Internet-facing SLB instance and opens ports 6443, 8443, and 22. If you enable SSH logon over the Internet when you create the cluster, port 22 is opened. Otherwise, port 22 is not exposed.

Limits

  • ACK clusters support only VPCs.
  • By default, each account has specific quotas on cloud resources that can be created. You cannot create clusters if the quota is reached. Make sure that you have sufficient resource quotas before you create a cluster.

    To request a quota increase, submit a ticket.

    • For more information, see Quota limits.
      Notice By default, you can add up to 48 route entries to a VPC. This means that you can deploy up to 48 nodes in an ACK cluster that uses Flannel. This limit does not apply to ACK clusters that use Terway. To deploy more nodes in a cluster, submit a ticket to apply for an increase on the quota of route entries in the VPC where the cluster is deployed.
    • By default, you can create at most 100 security groups with each account.
    • By default, you can create at most 60 pay-as-you-go SLB instances with each account.
    • By default, you can create at most 20 EIPs with each account.
  • Limits on ECS instances:

    The pay-as-you-go and subscription billing methods are supported.

    Note After an ECS instance is created, you can change its billing method from pay-as-you-go to subscription in the ECS console. For more information, see Change the billing method of an ECS instance from pay-as-you-go to subscription.

Procedure

  1. Log on to the ACK console.
  2. In the left-side navigation pane of the ACK console, click Clusters.
  3. In the upper-right corner of the Clusters page, click Cluster Template.
  4. In the Select Cluster Template dialog box, find Dedicated Cluster for Heterogeneous Computing in the Other Clusters section and click Create.
  5. On the Dedicated Kubernetes tab, configure the cluster.
    1. Configure basic settings of the cluster.
      Parameter Description
      Cluster Name
      Enter a name for the cluster.
      Note The name must be 1 to 63 characters in length, and can contain digits, letters, and hyphens (-).
      Region Select a region to deploy the cluster.
      Billing Method
      The pay-as-you-go and subscription billing methods are supported. If you select the subscription billing method, you must set the following parameters:
      Note If you set Billing Method to Subscription, only Elastic Compute Service (ECS) instances and Server Load Balancer (SLB) instances are billed on a subscription basis. Other cloud resources are billed on a pay-as-you-go basis. For more information about the billing rules of Alibaba Cloud resources, see Billing of cloud services.
      • Duration: You can select 1, 2, 3, or 6 months. If you require a longer duration, you can select 1 year, 2 years, or 3 years.
      • Auto Renewal: Specify whether to enable auto-renewal.
      Resource Group Move the pointer over All Resources at the top of the page and select the resource group to which the cluster belongs. The name of the selected resource group is displayed. Resource Group
      Kubernetes Version Select a Kubernetes version.
      Container Runtime

      The containerd, Docker, and Sandboxed-Container runtimes are supported. For more information, see Comparison of Docker, containerd, and Sandboxed-Container.

      VPC Select a virtual private cloud (VPC) to deploy the cluster. Standard VPCs and shared VPCs are supported.
      • Shared VPC: The owner of a VPC (resource owner) can share the vSwitches in the VPC with other accounts in the same organization.
      • Standard VPC: The owner of a VPC (resource owner) cannot share the vSwitches in the VPC with other accounts.
      Note ACK clusters support only VPCs. You can select a VPC from the drop-down list. If no VPC is available, click Create VPC to create one. For more information, see Create and manage a VPC.
      vSwitch Select vSwitches.

      You can select up to three vSwitches that are deployed in different zones. If no vSwitch is available, click Create vSwitch to create one. For more information, see Work with vSwitches.

      Network Plug-in
      Select a network plug-in. Flannel and Terway are supported. For more information, see Terway and Flannel.
      • Flannel: a simple and stable Container Network Interface (CNI) plug-in that is developed by open source Kubernetes. Flannel provides a few simple features. However, it does not support standard Kubernetes network policies.
      • Terway: a network plug-in that is developed by ACK. Terway allows you to assign elastic network interfaces (ENIs) of Alibaba Cloud to containers. It also allows you to customize Kubernetes network policies to regulate how containers communicate with each other and implement bandwidth throttling on individual containers.
        Note
        • The number of pods that can be deployed on a node depends on the number of ENIs that are attached to the node and the maximum number of secondary IP addresses that are provided by these ENIs.
        • If you select a shared VPC for a cluster, you must select Terway as the network plug-in.
        • If you select Terway, an ENI is shared among multiple pods. A secondary IP address of the ENI is assigned to each pod.
      IP Addresses per Node
      If you select Flannel as the network plug-in, you must set IP Addresses per Node.
      Note
      • IP Addresses per Node specifies the maximum number of IP addresses that can be assigned to each node. We recommend that you use the default value.
      • After you select the VPC and specify the number of IP addresses per node, recommended values are automatically generated for Pod CIDR Block and Service CIDR. The system also provides the maximum number of nodes that can be deployed in the cluster and the maximum number of pods that can be deployed on each node. You can modify the values based on your business requirements.
      Pod CIDR Block

      If you select Flannel as the network plug-in, you must set Pod CIDR Block.

      The CIDR block specified by Pod CIDR Block cannot overlap with that of the VPC or those of the existing clusters in the VPC. The CIDR block cannot be modified after the cluster is created. The Service CIDR block cannot overlap with the pod CIDR block. For more information about how to plan CIDR blocks for an ACK cluster, see Plan CIDR blocks for an ACK cluster.

      Terway Mode If you set Network Plug-in to Terway, the Terway Mode parameter is available.
      When you set Terway Mode, you can select or clear Assign One ENI to Each Pod.
      • If you select Assign One ENI to Each Pod, an elastic network interface (ENI) is assigned to each pod.
      • If you clear Assign One ENI to Each Pod, an ENI is shared among multiple pods. A secondary IP address of the ENI is assigned to each pod.
      Note To use this feature, submit a ticket to apply to be added to a whitelist.
      Pod vSwitch If you set Network Plug-in to Terway, the Pod vSwitch parameter is available. Pod vSwitch specifies vSwitches for pods. The ENI used by a pod must be deployed in the zone where the node that hosts the pod is deployed. Therefore, you must select another vSwitch in the zone where the node vSwitch is deployed to assign IP addresses to pods. To ensure sufficient IP addresses for all pods, we recommend that you set the subnet mask length of the CIDR block to a value no greater than 19 for the pod vSwitch.
      Service CIDR Set Service CIDR. The CIDR block specified by Service CIDR cannot overlap with that of the VPC or those of the existing clusters in the VPC. The CIDR block cannot be modified after the cluster is created. The Service CIDR block cannot overlap with the pod CIDR block. For more information about how to plan CIDR blocks for an ACK cluster, see Plan CIDR blocks for an ACK cluster.
      Configure SNAT Specify whether to configure SNAT rules for the VPC.
      • If the specified VPC has a NAT gateway, ACK uses this NAT gateway.
      • If the VPC does not have a NAT gateway, the system automatically creates one. If you do not want the system to create a NAT gateway, clear Configure SNAT for VPC. In this case, you must manually create a NAT gateway and configure SNAT rules to enable Internet access for the VPC. Otherwise, resources in the VPC cannot access the Internet and the cluster cannot be created.
      Access to API Server
      By default, an internal-facing SLB instance is created for the Kubernetes API server of the cluster. You can modify the specification of the SLB instance. For more information, see Instance types and specifications.
      Notice If you delete the SLB instance, you cannot access the Kubernetes API server of the cluster.
      Select or clear Expose API Server with EIP. The ACK API server provides multiple HTTP-based RESTful APIs, which can be used to create, delete, modify, query, and monitor resources, such as pods and Services.
      • If you select this check box, an elastic IP address (EIP) is created and associated with an SLB instance. Port 6443 used by the API server is opened on master nodes. You can connect to and manage the cluster by using kubeconfig files over the Internet.
      • If you clear this check box, no EIP is created. You can connect to and manage the cluster by using kubeconfig files only from within the VPC.
      SSH Logon

      To enable SSH logon, you must first select Expose API Server with EIP.

      • If you enable SSH logon over the Internet, you can access the cluster by using SSH.
      • If you disable SSH logon over the Internet, you cannot access the cluster by using SSH or kubectl. If you want to access an Elastic Compute Service (ECS) instance in the cluster by using SSH, you must manually associate an elastic IP address (EIP) with the instance and configure security group rules to open SSH port 22. For more information, see Connect to the master nodes of a dedicated Kubernetes cluster by using SSH.
      RDS Whitelist Configure the whitelist of the ApsaraDB RDS instance. Add the IP addresses of nodes in the cluster to a whitelist of the ApsaraDB RDS instance.
      Security Groups

      You can select Create Basic Security Group, Create Advanced Security Group, or Select Existing Security Group. For more information about security groups, see Overview.

    2. Configure advanced settings of the cluster.
      Parameter Description
      Time Zone

      Select a time zone for the cluster. By default, the time zone of your browser is selected.

      Kube-proxy Mode

      iptables and IPVS are supported.

      • iptables is a mature and stable kube-proxy mode. It uses iptables rules to conduct service discovery and load balancing. The performance of this mode is restricted by the size of the Kubernetes cluster. This mode is suitable for Kubernetes clusters that manage a small number of Services.
      • IPVS is a high-performance kube-proxy mode. It uses Linux Virtual Server (LVS) to conduct service discovery and load balancing. This mode is suitable for clusters that manage a large number of Services. We recommend that you use this mode in scenarios where high-performance load balancing is required.
      Labels

      Add labels to the cluster. Enter a key and a value, and then click Add.

      Note
      • Key is required. Value is optional.
      • Keys are not case-sensitive. A key cannot exceed 64 characters in length, and cannot start with aliyun, http://, or https://.
      • Values are not case-sensitive. A value cannot exceed 128 characters in length, and cannot start with http:// or https://. A value can be empty.
      • The keys of labels that are added to the same resource must be unique. If you add a label with a used key, this label overwrites the label that uses the same key.
      • If you add more than 20 labels to a resource, all labels become invalid. You must remove excess labels for the remaining labels to take effect.
      Cluster Domain Set the domain name of the cluster.
      Note The default domain name is cluster.local. You can enter a custom domain name. A domain name consists of two parts. Each part must be 1 to 63 characters in length and can contain only letters and digits. You cannot leave these parts empty.
      Custom Certificate SANs

      You can specify custom subject alternative names (SANs) for the API server certificate. Separate multiple IP addresses or domain names with commas (,).

      Service Account Token Volume Projection

      Enable Service Account Token Volume Projection to enhance security when you use service accounts. For more information, see Enable service account token volume projection.

      Cluster CA If you select this check box, upload a certificate authority (CA) certificate for the cluster to secure data transmission between the server and client.
      Deletion Protection Specify whether to enable deletion protection for the cluster. Deletion protection prevents the cluster from being accidentally deleted in the console or by calling the API. This prevents user errors.
  6. Click Next:Master Configurations to configure master nodes.
    Parameter Description
    Master Node Quantity Specify the number of master nodes. You can create three or five master nodes.
    Instance Type Select the instance type for master nodes. For more information, see Instance family.
    Note If no instance type is available, you can change vSwitches on the Cluster Configurations wizard page.
    System Disk By default, system disks are mounted to master nodes. Standard SSDs, enhanced SSDs, and ultra disks are supported.
    Note
    • You can select Enable Backup to back up disk data.
    • If you select enhanced SSD as the system disk type, you can set a custom performance level for the system disk.

      You can select higher performance levels for enhanced SSDs with larger storage capacities. For example, you can select performance level 2 for an enhanced SSD with a storage capacity of more than 460 GiB. You can select performance level 3 for an enhanced SSD with a storage capacity of more than 1,260 GiB. For more information, see Capacity and PLs.

  7. Click Next:Node Pool Configurations to configure worker nodes.
    1. Set worker instances.
      • If you select Create Instance, you must set the parameters as described in the following table.
        Parameter Description
        Node Pool Name
        The name of the node pool.
        Note The name must be 1 to 63 characters in length, and can contain digits, letters, and hyphens (-).
        Instance Type You must select the instance types for heterogeneous computing, including GPU-accelerated, FPGA-accelerated, and NPU-accelerated instances. For more information, see Instance family.
        Note If no instance type is available, you can change vSwitches on the Cluster Configurations wizard page.
        Selected Types The selected instance types are displayed.
        Quantity Specify the number of worker nodes.
        System Disk
        Enhanced SSDs, standard SSDs, and ultra disks are supported.
        Note
        • You can select Enable Backup to back up disk data.
        • If you select enhanced SSD as the system disk type, you can set a custom performance level for the system disk.

          You can select higher performance levels for enhanced SSDs with larger storage capacities. For example, you can select performance level 2 for an enhanced SSD with a storage capacity of more than 460 GiB. You can select performance level 3 for an enhanced SSD with a storage capacity of more than 1,260 GiB. For more information, see Capacity and PLs.

        Mount Data Disk

        Enhanced SSDs, standard SSDs, and ultra disks are supported. You can select Encrypt Disk and Enable Backup when you mount data disks.

        Operating System
        ACK supports the following node operating systems:
        • Alibaba Cloud Linux 2.x. This is the default operating system.
          If you select Alibaba Cloud Linux 2.x, you can configure security reinforcement for the operating system:
          • Disable: disables security reinforcement for Alibaba Cloud Linux 2.x.
          • CIS Reinforcement: enables security reinforcement for Alibaba Cloud Linux 2.x. For more information about Center for Internet Security (CIS) reinforcement, see CIS reinforcement.
        • CentOS 7.x
          Note CentOS 8.x or later are not supported.
        Logon Type
        • Key pair logon.
          • Key Pair: Select an SSH key pair from the drop-down list.
          • create a key pair: Create an SSH key pair if none is available. For more information about how to create an SSH key pair, see Create an SSH key pair. After the key pair is created, set it as the credential that is used to log on to the cluster.
        • Password logon.
          • Password: Enter the password that is used to log on to the nodes.
          • Confirm Password: Enter the password again.
          Note The password must be 8 to 30 characters in length, and must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters. The password cannot contain underscores (_).
      • If you select Add Existing Instance, you must select ECS instances that are deployed in the specified region. Then, set the Operating System, Logon Type, and Key Pair parameters based on the preceding description.
    2. Configure advanced settings.
      Parameter Description
      Node Protection Specify whether to enable node protection.
      Note By default, this check box is selected. Node protection prevents nodes from being accidentally deleted in the console or by calling the API. This prevents user errors.
      User Data For more information, see Overview of ECS instance user data.
      Custom Node Name Specify whether to use a custom node name.
      A node name consists of a prefix, an IP substring, and a suffix.
      • The prefix and suffix can contain multiple parts that are separated by periods (.). Each part can contain lowercase letters, digits, and hyphens (-), and must start and end with a digit or lowercase letter.
      • The IP substring length specifies the number of digits to be truncated from the end of the node IP address. The IP substring length ranges from 5 to 12.

      For example, if the node IP address is 192.168.0.55, the prefix is aliyun.com, the IP substring length is 5, and the suffix is test, the node name will be aliyun.com00055test.

      Custom Image
      • You can select a custom ECS image. After you select a custom image, all nodes in the cluster are deployed by using this image. For more information about how to create a custom image, see Create a Kubernetes cluster by using a custom image.
      • You can select a shared ECS image. After you select a shared image, all nodes in the cluster are deployed by using this image. For more information about shared images, see Share a custom image.
      Note
      • Only custom images based on CentOS 7.x and Alibaba Cloud Linux 2.x are supported.
      • To use this feature, submit a ticket to apply to be added to a whitelist.
      Node Port Range Set the node port range. The supported ports range from 30000 to 65535.
      CPU Policy Set the CPU policy.
      • None: uses the default CPU affinity. This is the default policy.
      • Static: allows pods with specific resource characteristics on the node to be granted with enhanced CPU affinity and exclusivity.
      Taints Add taints to all worker nodes in the cluster.
  8. Click Next:Component Configurations to configure components.
    Parameter Description
    Ingress Specify whether to install an Ingress controller. By default, Install NGINX Ingress Controller is selected. For more information, see Advanced NGINX Ingress configurations.
    Service Discovery

    Specify whether to install NodeLocal DNSCache. By default, NodeLocal DNSCache is installed.

    NodeLocal DNSCache runs a Domain Name System (DNS) caching agent to improve the performance and stability of DNS resolution. For more information about NodeLocal DNSCache, see Configure NodeLocal DNSCache.

    Volume Plug-in Select a volume plug-in. FlexVolume and CSI are supported. ACK clusters can be automatically bound to Alibaba Cloud disks, Apsara File Storage NAS (NAS) file systems, and Object Storage Service (OSS) buckets that are mounted to pods in the clusters. For more information, see Storage management-FlexVolume and Storage management-CSI.
    Monitoring Agents

    Specify whether to install the CloudMonitor agent. You can select Install CloudMonitor Agent on ECS Instance. After the CloudMonitor agent is installed, you can view monitoring information about ECS instances in the CloudMonitor console.

    Log Service

    Specify whether to enable Log Service. You can select an existing Log Service project or create one.

    If you select Enable Log Service, the Log Service plug-in is automatically installed in the cluster. You can set up Log Service with a few steps when you deploy an application. For more information, see Collect log data from containers by using Log Service.

    After you select Enable Log Service, you can specify whether to select Create Ingress Dashboard and Install node-problem-detector and Create Event Center.

    Workflow Engine Specify whether to enable Alibaba Cloud Genomics Service (AGS).
    Note To use this feature, you must first submit a ticket.
    • If you select this check box, the system automatically installs the AGS workflow plug-in when the system creates the cluster.
    • If you clear this check box, you must manually install the AGS workflow plug-in. For more information, see Introduction to AGS CLI.
  9. Click Next:Confirm Order.
  10. Select Terms of Service and click Create Cluster.
    Note It requires approximately 10 minutes for the system to create an ACK managed cluster that contains multiple nodes.

What to do next

After the cluster is created, go to the Clusters page, find the created cluster, and then click the cluster name or click Details in the Actions column. In the left-side navigation pane of the details page, choose Nodes > Nodes. On the page that appears, select a worker node and choose More > Details in the Actions column. Then, you can view the GPUs that are provided by the node.