Professional edge Kubernetes clusters offer higher reliability, security, and schedulability than standard edge Kubernetes clusters. In addition, professional edge Kubernetes clusters are covered by the service level agreement (SLA) that supports compensation clauses. This type of cluster is suitable for enterprise users who require high stability and security for large-scale workloads. This topic describes how to create a professional edge Kubernetes cluster in the Container Service for Kubernetes (ACK) console.

Prerequisites

Resource Access Management (RAM) is activated in the RAM console. Auto Scaling is activated in the Auto Scaling console.

Note

When you create a Container Service for Kubernetes (ACK) cluster, take note of the following limits:

  • Server Load Balancer (SLB) instances that are created along with an ACK cluster support only the pay-as-you-go billing method.
  • ACK clusters support only virtual private clouds (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.
    • For more information about the maximum numbers of clusters and nodes that can be created with each account, see Limits.
    • 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 elastic IP addresses (EIPs) with each account.

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 Create Kubernetes Cluster.
  4. On the Managed Edge Kubernetes tab, configure the professional edge Kubernetes cluster.
    1. Configure basic settings of the cluster.
      Parameter Description
      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 Groups
      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 specifications

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

      Select Professional to create a professional edge Kubernetes cluster.

      Region

      Select a region to deploy the ACK cluster.

      Kubernetes Version

      The Kubernetes versions that are supported by professional edge Kubernetes clusters are displayed.

      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 Work with VPCs.
      VSwitch

      Select vSwitches.

      You can select at most 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.

      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 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 Plan CIDR blocks for an ACK cluster.

      Service CIDR

      Set Service CIDR. The CIDR block 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 Plan CIDR blocks for an ACK cluster.

      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.

      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 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.
      Note Edge nodes interact with the API server in the cloud over the Internet. If you clear Expose API Server with EIP, the edge nodes cannot connect to the cluster in the cloud. As a result, the created cluster cannot be used in edge computing scenarios.
      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 same VPC as the ACK cluster.
      Security Group

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

      Deletion Protection
    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 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 ACK 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
      Add 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 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.
      Secret Encryption If you select Select Key, you can use a key that is created in the Key Management Service (KMS) console to encrypt Kubernetes Secrets. For more information, see Use KMS to encrypt Kubernetes Secrets.
  5. Click Next:Worker Configurations to configure worker nodes.
    Note In a professional edge Kubernetes cluster, you must configure at least one worker node to deploy controllers.
    Parameter Description
    Instance Type

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

    Note To use advanced features such as logging, monitoring, and reverse tunneling, you must deploy the related components in the cloud. Therefore, you must create at least one Elastic Compute Service (ECS) instance as a worker node.
    Selected Types

    The selected instance types are displayed.

    Quantity

    Specify the number of worker nodes to be created.

    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.

    Logon Type
    • Set the key pair.
      • 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:
      • Password: Enter the password that is used to log on to the nodes.
      • Confirm Password: Enter the password again.
    Note You must set the logon type if you select Install CloudMonitor Agent on ECS Instance or Enable Log Service.
  6. Click Next:Component Configurations to configure components.
    Parameter Description
    CloudMonitor Agent

    Select whether to install the CloudMonitor agent. If you select Install the CloudMonitor Agent on ECS Nodes, you can view monitoring data about the nodes in the CloudMonitor console.

    Log Service

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

  7. Click Next:Confirm Order.
  8. Read Terms of Service, select the check box, and then click Create Cluster.
    Note It requires about 10 minutes to create a professional edge Kubernetes cluster that contains multiple nodes.

Result

  • After the cluster is created, you can view the created cluster on the Clusters page in the ACK console.
  • Click View Logs in the Actions column. On the Log Information page, you can view the cluster log. To view detailed log information, click Stack events.

  • 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. You can also 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 API server uses to provide services over the Internet. It allows you to manage the cluster by using kubectl or other tools on your terminal.
    • API Server Internal Endpoint: the IP address and port that the API server uses to provide services within the cluster. The IP address belongs to the SLB instance that is bound to the cluster.
    • Testing Domain: the domain name that is used to test Services. The suffix of the domain name is <cluster_id>.<region_id>.alicontainer.com.
      Note On the Basic Information tab, you can click Rebind Domain Name on the right side of Testing Domain to rebind the domain name.