Container Service for Kubernetes (ACK) automatically creates and manages master nodes for managed Kubernetes clusters. This allows you to focus on business development. This topic describes how to create a managed Kubernetes cluster in the ACK console.

Prerequisites

Log on to the Resource Access Management (RAM) console and the Auto Scaling (ESS) console to activate the relevant cloud services.

Note

When you create an ACK cluster, take note of the following limits:

  • Server Load Balancer (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 clouds (VPCs).
  • Each account can consume only a limited amount of computing resources. Clusters cannot be created if your computing resources are insufficient. To increase the quota of computing resources for your account, submit a ticket.
    • You can create up to 50 clusters across all regions under each account. A cluster can contain up to 100 nodes. To increase the quota of clusters or nodes,submit a ticket.
      Note By default, you can add up to 48 route entries to the VPC where an ACK cluster is deployed. This means that you can configure up to 48 route entries for an ACK cluster 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.
  • Limits on Elastic Compute Service (ECS) instances:

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

Procedure

  1. Log on to the Container Service for Kubernetes (ACK) console.
  2. In the left-side navigation pane, click Clusters.
  3. In the upper-right corner of the Clusters page, click Create Kubernetes Cluster. In the Select Cluster Template dialog box, find Standard Managed Cluster and click Create.
  4. On the Managed Kubernetes tab, set the cluster parameters.
    1. Configure basic settings of the cluster.
      Parameter Description
      Cluster Name
      Enter a name for the ACK cluster.
      Note The name must be 1 to 63 characters in length. It can contain digits, letters, and hyphens (-).
      Cluster Specification

      Select a cluster type. Standard edition and Professional are supported.

      Region

      Select a region to deploy the ACK cluster.

      Resource Group
      Move the pointer over All Resources at the top of the page and select the resource group to which the ACK cluster belongs. The name of the selected resource group appears on the page.Resource Group
      Time Zone

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

      Kubernetes Version

      Select a Kubernetes version.

      Container Runtime

      Docker and Sandboxed-Container are supported.

      VPC
      Select a virtual private cloud (VPC) to deploy the ACK cluster. Shared VPCs and standard VPCs are supported.
      • Shared VPC: The owner of a VPC (resource owner) can share vSwitches in the VPC under the account of the owner with other accounts in the same organization.
      • Standard VPC: The owner of a VPC (resource owner) cannot share vSwitches in the VPC under the account of the owner 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 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 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 that is developed by the Kubernetes community. 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 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 that are provided by these ENIs.
        • If you select a shared VPC for an ACK 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.
      Terway Mode
      If you select Terway, you must set Terway Mode.
      • Select or clear Assign One ENI to Each Pod.
        • If you select the check box, an ENI is assigned to each pod.
        • If you clear the check box, an ENI is shared among multiple pods. A secondary IP address that is provided by the ENI is assigned to each pod.
      • Select or clear IPVLAN.
        • This option is available only when you clear Assign One ENI to Each Pod.
        • If you select IPVLAN, IPVLAN and extended Berkeley Packet Filter (eBPF) are used for network virtualization when an ENI is shared among multiple pods. This improves network performance. Only the Alibaba Cloud Linux 2 operating system is supported.
        • If you clear IPVLAN, policy-based routes are used for network virtualization when an ENI is shared among multiple pods. The CentOS 7 and Alibaba Cloud Linux 2 operating systems are supported. This is the default setting.
        Note Assign One ENI to Each Pod and IPVLAN are available to only users in the whitelist.If you are not in the whitelist, submit a ticket.
      • Select or clear Support for NetworkPolicy.
        • The NetworkPolicy feature is available only when you clear Assign One ENI to Each Pod. By default, Assign One ENI to Each Pod is unselected.
        • If you select Support for NetworkPolicy, you can use Kubernetes network policies to control communication among pods
        • If you clear Support for NetworkPolicy, you cannot use Kubernetes network policies to control communication among pods. This prevents Kubernetes network policies from posing heavy loads on the Kubernetes API server.
      Pod VSwitch

      If you select Terway, you must allocate vSwitches to pods. Each pod vSwitch must correspond to a worker vSwitch.

      Pod CIDR Block

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

      The CIDR block that is specified by Pod CIDR Block cannot overlap with that of the VPC or existing ACK clusters in the VPC. 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.

      Service CIDR

      Set Service CIDR. The CIDR block that is specified by Service CIDR cannot overlap with that of the VPC or existing ACK clusters in the VPC. 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, an ACK cluster cannot be accessed over the Internet. If the VPC that you select for the ACK 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.

      Access to API Server
      By default, an internal-facing SLB instance is created for the API server. You can modify the specifications of the SLB instance. For more information, see Specification.
      Notice If you delete the SLB instance, you cannot access the API server.
      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 attached to a public-facing Server Load Balancer (SLB) instance. Port 6443 used by the API server is opened on master nodes. You can connect to and manage the ACK cluster by using kubeconfig over the Internet.
      • If you clear this check box, no EIP is created. You can connect to and manage the ACK cluster only by using kubeconfig from within the VPC.
      RDS Whitelist
      Set the Relational Database Service (RDS) whitelist. Add the IP addresses of nodes in the ACK cluster to the RDS whitelist.
      Note To enable an RDS instance to access the ACK cluster, you must deploy the RDS instance in the VPC where the ACK cluster is deployed.
      Security Group

      You can select Create Basic Security Group, Create Advanced Security Group, or 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 ACK cluster. This mode is suitable for ACK 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 ACK 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 nodes. Enter a key and a value, 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://. This parameter 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, the label overwrites the one that uses the same key.
      • You can add up to 20 labels to each resource. If you add more than 20 labels to a resource, all labels become invalid. You must remove unused labels for the remaining labels to take effect.
      Cluster Domain
      Set the domain name of the ACK 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 enter custom subject alternative names (SANs) for the API server certificate of the cluster to accept requests from specified IP addresses or domain names.

      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.

      Deletion Protection

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

  5. Click Next:Worker Configurations to configure worker nodes.
    1. Set worker nodes.
      • If you select Create Instance, you must set the parameters that are listed in the following table.
        Parameter Description
        Billing Method
        The pay-as-you-go and subscription billing methods are supported. If you select pay-as-you-go, you must set the following parameters:
        • Duration: You can select 1, 2, 3, or 6 months. If you require a longer duration, you can select 1 to 5 years.
        • Auto Renewal: Specify whether to enable auto-renewal.
        Instance Type

        You can select multiple instance types. For more information, see Instance families.

        Selected Types

        The selected instance types are displayed.

        Quantity

        Specify the number of worker nodes to be created.

        Note We recommend that you configure at least two worker nodes. You can add or delete worker nodes based on your business requirements after the cluster is created. If the cluster has only one worker node or contains low-specification worker nodes, cluster components may not run as expected.
        System Disk
        Enhanced SSDs, SSDs, and ultra disks are supported.
        Note You can select Enable Backup to back up disk data.
        Mount Data Disk

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

        Operating System
        ACK supports the following node operating systems:
        • Alibaba Cloud Linux 2. This is the default setting.
        • 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 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 that is used to log on to the ACK cluster.
        • Password logon.
          • Password: Enter the password that is used to log on to the nodes.
          • Confirm Password: Enter the password again.
      • If you select Add Existing Instance, you must select ECS instances that are deployed in the region where the cluster is deployed. Then, set Operating System, Logon Type, and Key Pair based on the preceding settings.
    2. Configure advanced settings for worker nodes.
      Parameter Description
      Node Protection
      Specify whether to enable node protection.
      Note By default, this check box is selected. The nodes in the ACK cluster cannot be deleted in the console or by calling the API. This prevents user errors.
      User Data

      For more information, see Prepare user data.

      Custom Image
      You can select a custom image for your nodes. After you select a custom image, all nodes in the cluster are deployed by using the image. For more information about how to create a custom image, see Create a Kubernetes cluster by using a custom image.
      Note
      • Only custom images based on CentOS 7.x and Alibaba Cloud Linux 2.x are supported.
      • This feature is available to only users in the whitelist. If you are not in the whitelist, submit a ticket.
      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 (.). 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.

      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 specific resource characteristics on the node to be granted with enhanced CPU affinity and exclusivity.
      Taints

      Add taints to worker nodes in the ACK cluster.

  6. 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 a volume plug-in. FlexVolume and CSI are supported. An ACK cluster can be automatically bound to cloud disks of Alibaba Cloud, Network Attached Storage (NAS) file systems, and Object Storage Service (OSS) buckets that are mounted to pods in the cluster. For more information, see Storage management-Flexvolume and 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 data about the nodes in the Cloud Monitor console.

    Log Service

    Specify whether to enable Log Service. You can select an existing Log Service project or create a new one. By default, Enable Log Service is selected. When you create an application, you can perform a few steps to enable Log Service. For more information, see Use Log Service to collect container logs.

    You can also select or clear Collect Logs of Control Plane Components. If you select this check box, logs of components on the ACK control plane are collected to the Log Service project under your account. For more information, see 收集托管集群控制平面组件日志.
    Note By default, Collect Logs of Control Plane Components is selected for a professional managed Kubernetes cluster.

    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 enable Alibaba Cloud Genomics Compute Service (AGS).
    • If you select this check box, the system automatically installs the AGS workflow plug-in when the system creates the ACK cluster.
    • If you clear this check box, you must manually install the AGS workflow plug-in. For more information, see Introduction to AGS CLI.
  7. Click Next:Confirm Order.
  8. Select Terms of Service and click Create Cluster.
    Note It requires about 10 minutes to create an ACK cluster that contains multiple nodes.

Result

  • After the cluster is created, you can find the 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 created cluster and click Details in the Actions column. On the details page, 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.

      Bind EIP and Unbind EIP: These options are available to only managed Kubernetes clusters.

      • Bind EIP: You can select an existing EIP or create one.

        The API server restarts after you bind an EIP to the API server. We recommend that you do not perform operations on the cluster during the restart process.

      • Unbind EIP: You cannot access the API server over the Internet after you unbind the EIP.

        The API server restarts after you unbind the EIP from the API server. We recommend that you do not perform operations on the cluster during the restart process.

    • API Server Internal Endpoint: the IP address and port that the Kubernetes API server uses to provide services within the cluster.
    • 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.Node information