This topic describes how to create a dedicated Kubernetes cluster that runs sandboxed containers in the Container Service for Kubernetes (ACK) console.

Limits

  • SLB instances that are created together with the ACK cluster support only the pay-as-you-go billing method.
  • ACK clusters support only Virtual Private Cloud (VPC) networks.
  • Each account can consume only a limited amount of computing resources. You fail to create clusters if you do not have sufficient computing resources. When you create clusters, make sure that you have sufficient resources. To increase the quota of computing resources for your account, submit a ticket.
    • You can create up to five clusters across regions for each account. You can deploy up to 40 nodes in each cluster. To increase the quota of clusters or nodes, submit a ticket.
      Notice By default, you can add up to 48 route entries to a VPC . This means that you can configure up to 48 route entries for ACK clusters that are deployed in a VPC. To increase the quota of route entries for a VPC, submit a ticket.
    • You can create up to 100 security groups under each account.
    • You can create up to 60 pay-as-you-go SLB instances under each account.
    • You can create up to 20 elastic IP addresses (EIPs) under each account.
  • To create an ACK cluster that supports sandboxed containers, you must set the parameters as required in the following table.
    Parameter Description
    Zone Select a zone where Elastics Compute Service (ECS) Bare Metal instances are deployed. Sandboxed containers support only ECS Bare Metal instances.
    Kubernetes Version Select 1.14.6-aliyun.1 or later.
    Container Runtime Select Sandboxed-Container.
    Worker Instance Add worker nodes by creating new ECS instances.
    Billing Method Select the subscription billing method.
    Instance Type Select ECS Bare Metal instances.
    Mount Data Disk Mount a data disk of 200 GiB at least. We recommend that you mount a data disk of 1 TB or larger.
    Operating System By default, the AliyunLinux operating system is used. You cannot not change the operating system.

Procedure

  1. Log on to the ACK console.
  2. In the left-side navigation pane, click Clusters.
  3. On the Clusters page, click Create Kubernetes Cluster in the upper-right corner of the page.
  4. In the Select Cluster Template dialog box, find Standard Dedicated Cluster and click Create in the Other Clusters section.
  5. On the ACK proprietary edition tab, configure the cluster.
    1. Configure basic settings of the cluster.
      Parameter Description
      Cluster Name
      Enter a name for the cluster of Container Service for Kubernetes (ACK).
      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.

      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 appears on the page.Resource Groups
      Kubernetes Version Select a Kubernetes version.
      Container Runtime Select Sandboxed-Container.
      VPC
      Select a Virtual Private Cloud (VPC) network to deploy the cluster. Shared VPC networks and standard VPC networks are supported.
      • Shared VPC network: The owner of a VPC network (resource owner) can share VSwitches in the VPC network under the account of the owner with other accounts in the same organization.
      • Standard VPC network: The owner of a VPC network (resource owner) cannot share VSwitches in the VPC network under the account of the owner with other accounts.
      Note ACK clusters support only VPC networks. You can select a VPC network from the drop-down list. If no VPC network is available, click Create VPC to create one. For more information, see Create a VPC.
      VSwitch

      Select VSwitches.

      You can select up to three VSwitches deployed in different zones. If no VSwitch is available, click Create VSwitch to create one. For more information, see Create a VSwitch.

      Network Plug-in
      Select a network plug-in. Both Flannel and Terway are supported. For more information, see Flannel and Terway.
      • Flannel: a simple and stable Container Network Interface (CNI) plug-in developed by the Kubernetes community. Flannel offers a few simple features and does not support standard Kubernetes network policies.
      • Terway: a network plug-in developed by ACK. Terway allows you to assign Alibaba Cloud elastic network interfaces (ENIs) to containers. It also allows you to customize Kubernetes network policies to control intercommunication among containers, 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 provided by these ENIs.
        • If you select a shared VPC network for a cluster, you must select the Terway 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.
      Pod CIDR Block

      If you select Flannel, you must set Pod CIDR Block.

      The CIDR block specified by Pod CIDR Block cannot overlap with that of the VPC network or existing ACK clusters in the VPC network. The CIDR Block cannot be modified after it is specified. The Service CIDR block cannot overlap with the Pod CIDR block. For more information about subnetting for ACK clusters, see Assign CIDR blocks to resources in a Kubernetes cluster under a VPC.

      Pod VSwitch

      If you select Terway, you must allocate VSwitches to pods. Each pod VSwitch must correspond to a worker VSwitch.

      Elastic network interfaces (ENIs) must be deployed in the zone where the ENI devices are located. Therefore, you must select another VSwitch for the pods in the cluster. When the cluster provides services, the VSwitch assigns IP addresses to the pods. To ensure that there are sufficient IP addresses for all pods, we recommend that you set the mask length of the CIDR block to a value no greater than 19 for the VSwitch.

      Service CIDR

      Set Service CIDR. The CIDR block specified by Service CIDR cannot overlap with that of the VPC network or existing ACK clusters in the VPC network. The CIDR block cannot be modified after it is specified. The Service CIDR block cannot overlap with the Pod CIDR block. For more information about subnetting for ACK clusters, see Assign CIDR blocks to resources in a Kubernetes cluster under a VPC.

      IP Addresses per Node
      If you select Flannel, you must set the number of 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.
      Configure SNAT

      By default, a cluster is not accessible over the Internet. If the VPC network that you select for the cluster cannot access the Internet, you can select Configure SNAT for VPC. Then, ACK creates a Network Address Translation (NAT) gateway and configures Source Network Address Translation (SNAT) entries to enable Internet access for the VPC network.

      Public Access

      Specify whether to expose the API server with an elastic IP address (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 EIP is created and attached to an internal Server Load Balancer (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 over the Internet.
      • If you clear this check box, no EIP is created. You can connect to and manage the cluster only by using kubeconfig from within the VPC network.
      SSH Logon

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

      • If you select this check box, you can use SSH to connect to the cluster.
      • If you clear this check box, you cannot use SSH or kubectl to connect to the cluster. If you want to access an ECS instance in the cluster by using SSH, you must manually attach an EIP to the instance and configure security group rules to open SSH port 22. For more information, see Use SSH to connect to an ACK cluster.
      RDS Whitelist
      Set the Relational Database Service (RDS) whitelist. Add the IP addresses of cluster nodes to the RDS whitelist.
      Note To enable an RDS instance to access an ACK cluster, you must deploy the RDS instance in the same VPC network as the ACK cluster.
      Security Group

      You can select Create Basic Security Group, Create Advanced Security Group, and Select Existing Security Group. For more information, see Overview.

    2. Configure advanced settings of the cluster.
      Parameter Description
      Kube-proxy Mode
      IPVS and iptables are supported.
      • iptables is a 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 cluster. This mode is suitable for clusters that run 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 run a large number of Services. We recommend that you use this mode in scenarios where high-performance load balancing is required.
      Labels
      Attach labels to nodes. Enter keys and values, and then click Add.
      Note
      • Key is required. Value is optional.
      • Keys are not case-sensitive. A key must be 1 to 64 characters in length, and cannot start with aliyun, http://, or https://.
      • Values are not case-sensitive. A value must be 1 to 128 characters in length, and cannot start with http:// or https://.
      • The keys of labels that are attached to the same resource must be unique. If you add a label with a used key, the label overwrites the one using the same key.
      • You can attach up to 20 labels to each resource. If you attach more than 20 labels to a resource, all labels become invalid. You must detach unused labels for the remaining labels to take effect.
      Cluster Domain
      Set the cluster domain.
      Note The default cluster domain is cluster.local. You can enter a custom domain. A domain consists of two parts. Each part must be 1 to 63 characters in length, and can contain only letters and digits.
      Custom Certificate SANs

      You can enter custom subject alternative names (SANs) for the API server of the cluster to accept requests from specified IP addresses or domains.

      Service Account Token Volume Projection

      Service account token volume projection reduces security risks when pods use service accounts to access the API server. This feature enables kubelet to request and store the token on behalf of the pod. This feature also allows you to configure token properties, such as the audience and validity duration. For more information, see Deploy service account token volume projection.

      Cluster CA If you select this check box, upload a Certificate Authority (CA) certificate for the ACK cluster to ensure secure data transmission between the server and client.
      Deletion Protection

      Specify whether to enable deletion protection. If you select this check box, the cluster cannot be deleted in the console or by calling the API. This allows you to avoid user errors.

  6. Click Next:Master Configurations to configure master nodes.
    Parameter Description
    Billing Method Select Subscription.
    Note Worker instances support only ECS Bare Metal instances. ECS Bare Metal instances support only the Subscription billing method. The pay-as-you-go billing method is not supported by ECS Bare Metal instances.
    Duration Select the duration of the subscription.
    Auto Renewal Specify whether to enable auto renewal.
    Master Node Quantity Select the number of master nodes. You can create three or five master nodes.
    Instance Type Select an instance type for each master node. For more information, see Instance families.
    System Disk By default, system disks are mounted to master nodes. SSDs and ultra disks are supported.
    Note You can select Enable Backup to back up disk data.
  7. Click Next:Worker Configurations to configure worker nodes.
    1. Configure basic settings of worker nodes.
      Parameter Description
      Worker Instance By default, Create Instance is selected. You cannot select Add Existing Instance.
      Instance Type Select ECS Bare Metal instances. Only ECS Bare Metal instances are supported.
      Selected Types The selected instance type is displayed here. You can select only ECS Bare Metal Instance as the instance type.
      Quantity

      Specify the number of worker nodes to be created.

      System Disk
      ESSDs, SSDs, and ultra disks are supported.
      Note You can select Enable Backup to back up disk data.
      Mount Data Disk

      ESSDs, SSDs, and ultra disks are supported. You can enable disk encryption and backup when you add data disks.

      Notice The data disk is used to store the root file system of all containers on the node. Therefore, you must mount a data disk of at least 200 GiB. We recommend that you mount a data disk of at least 1 TB.
      Operating System By default, the AliyunLinux operating system is used. You cannot change the operating system.
      Logon Type
      • Key Pair:
        • Key Pair: Select an SSH key pair from the drop-down list.
        • create a key pair: Create a key pair if no SSH key pair 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 for logging on to the cluster.
      • Password:
        • Password: Enter a password for logging on to the nodes.
        • Confirm Password: Enter the password again.
    2. Configure advanced settings of worker nodes.
      Parameter Description
      Node Protection
      Specify whether to enable node protection.
      Note By default, this check box is selected. This way, cluster nodes cannot be deleted in the console or by calling the API. This allows you to avoid user errors.
      User Data

      For more information, see Prepare 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.
      • Both the prefix and suffix can contain one or more parts that are separated with periods (.) and must start and end with a lowercase letter or digit. These parts can contain lowercase letters, digits, and hyphens (-), and must start and end with a lowercase letter or digit.
      • The IP substring length specifies the number of digits to be truncated from the end of the returned node IP address. Valid values: 5 to 12.

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

      Node Port Range Specify the node port range.
      CPU Policy
      Set the CPU policy.
      • none: This policy indicates that the default CPU affinity is used. This is the default policy.
      • static: This policy allows pods with certain resource characteristics on the node to be granted with enhanced CPU affinity and exclusivity.
      Taints

      Add taints to worker nodes in the cluster.

  8. Click Next:Component Configurations to configure components.
    Parameter Description
    Ingress

    Specify whether to install Ingress controllers. By default, Install Ingress Controllers is selected. For more information, see Configure an Ingress.

    Volume Plug-in Select CSI. Only CSI is supported by ACK clusters that run sandboxed containers. Disks, Network Attached Storage (NAS) file systems, and Object Storage Service (OSS) buckets provided by Alibaba Cloud can be automatically attached to pods of ACK clusters. For more information, see Storage management-CSI.
    Monitoring Agents

    Specify whether to install the Cloud Monitor agent. By default, Install CloudMonitor Agent on ECS Instance and Enable Prometheus Monitoring are selected. After the Cloud Monitor agent is installed on ECS nodes, you can view monitoring information about the nodes in the Cloud Monitor console.

    Log Service

    Specify whether to activate Log Service. You can select an existing Log Service project or create a Log Service project.

    By default, Enable Log Service is selected. When you create an application, you can activate Log Service through a few steps. For more information, see Use Log Service to collect container logs.

    By default, Install node-problem-detector and Create Event Center is selected. You can also specify whether to create Ingress dashboard in the Log Service console.

    Workflow Engine
    Specify whether to activate Alibaba Cloud Genomics Compute Service (AGS).
    • If you select this check box, the system automatically installs the AGS workflow plug-in when it 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 takes approximately 10 minutes for the system to create a Kubernetes cluster that consists of multiple nodes.

Result

  • After the cluster is created, you can view the created cluster on the Clusters page in the console.
  • Click View Logs in the Actions column. On the Log Information page, you can view cluster logs. To view detailed log information, click Stack events.
  • On the Clusters page, find the newly created cluster and click Details in the Actions column. On the details page of the cluster, click the Basic Information tab to view basic information about the cluster and click the Connection Information tab to view information about how to connect to the cluster.
    The following information is displayed:
    • API Server Public Endpoint: the IP address and port that the Kubernetes API Server uses to provide services over the Internet. It allows you to manage the cluster by using kubectl or other tools on the client.
    • API Server Internal Endpoint: the IP address and port that the Kubernetes API Server uses to provide services within the cluster. The endpoint belongs to the SLB instance bound to the cluster. Three master nodes work as the backend servers of the SLB instance.
    • Testing Domain: the domain name that is used for service testing. The suffix of the domain is <cluster_id>.<region_id>.alicontainer.com.
      Note To rebind the domain name, click Rebind Domain Name.
  • You can use kubectl and run the kubectl get node command to connect to the cluster and view information about the nodes in the cluster. For more information, see Use kubectl to connect to an ACK cluster.
    Nodes information