Professional managed Kubernetes clusters offer higher reliability, stability, security, and schedulability than standard managed Kubernetes clusters in large-scale production environments for enterprise users. In addition, professional managed Kubernetes clusters are covered by the service level agreement (SLA) that supports compensation clauses. This topic describes how to create a professional managed Kubernetes cluster in the Container Service for Kubernetes (ACK) console.
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 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
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 up to 100 security groups with each account.
- By default, you can create up to 60 pay-as-you-go SLB instances with each account.
- By default, you can create up to 20 elastic IP addresses (EIPs) with each account.
- Log on to the ACK console.
- In the left-side navigation pane of the ACK console, click Clusters.
- In the upper-right corner of the Clusters page, click Cluster Templates.
- In the Select Cluster Template dialog box, select Professional Managed Kubernetes Cluster and click Create.
- On the Managed Kubernetes tab, configure the cluster.
- Configure basic settings of the cluster.
Parameter Description Cluster NameEnter a name for the ACK cluster.Note The name must be 1 to 63 characters in length, and can contain digits, letters, and hyphens (-). Cluster Specification
Select a cluster type. You can select Standard edition or Professional.
Select Professional to create a professional managed Kubernetes cluster.
Select a region to deploy the cluster.
Resource GroupMove 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, as shown in the following figure. Kubernetes Version
The Kubernetes versions that are supported by ACK.
The containerd, Docker, and Sandboxed-Container runtimes are supported. For more information, see How do I choose between Docker and Sandboxed-Container?.
VPCSelect a virtual private cloud (VPC) to deploy the cluster. Standard VPCs and shared VPCs are supported.
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.
- 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.
Network Plug-inSelect a network plug-in. Flannel and Terway are supported. For more information, see Comparison between Flannel and Terway.
- 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.
- 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 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 NodeIf 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 block. 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 subnetting for ACK clusters, see Plan CIDR blocks for an ACK cluster.
Terway ModeIf you set Network Plug-in to Terway, you must set Terway Mode.
Select or clear Assign One ENI to Each Pod.
Note To select the Assign One ENI to Each Pod check box, you must submit a ticket to apply for this option to be available for your account.
- 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.
For more information about the IPVLAN feature in Terway mode, see Work with Terway.
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 the communication among pods.
- If you clear Support for NetworkPolicy, you cannot use Kubernetes network policies to control the communication among pods. This prevents Kubernetes network policies from overloading the Kubernetes API server.
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 subnetting for ACK clusters, see Plan CIDR blocks for an ACK cluster.
By default, an ACK cluster cannot access the Internet. If the VPC that you select for the ACK cluster cannot access the Internet, you can select Configure SNAT for VPC. This way, ACK will create a NAT gateway and configure Source Network Address Translation (SNAT) rules to enable Internet access for the VPC.
Access to API ServerBy default, an internal-facing Server Load Balancer (SLB) instance is created for the cluster API server. 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 cluster 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 associated with an Internet-facing 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 by using kubeconfig only within the VPC.
RDS WhitelistSet the Relational Database Service (RDS) whitelist. Add the IP addresses of the nodes in the cluster to the RDS whitelist.Note To enable an RDS instance to access the cluster, you must deploy the RDS instance in the VPC where the cluster is deployed. Security Group
- Configure advanced settings of the cluster.
Parameter Description Time Zone
Select a time zone for the ACK cluster. By default, the time zone configured for your browser is selected.
Kube-proxy Modeiptables 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 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.
LabelsAdd labels to the cluster. Enter a key and a value, and 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 can be empty and can contain up to 128 characters in length. It cannot be 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 others that use 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 other labels to take effect.
Cluster DomainSet 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 enter custom subject alternative names (SANs) for the API server certificate of the cluster to accept requests from specified IP addresses or domain names.
For more information, see Customize the SAN of the API server certificate for a managed Kubernetes cluster.
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 Enable service account token volume projection.
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 at rest in the etcd. Deletion Protection
Specify whether to enable deletion protection. Deletion protection prevents the cluster from being accidentally deleted in the console or by calling the API. This prevents user errors.
- Configure basic settings of the cluster.
- Click Next:Worker Configurations to configure worker nodes.
- Set Worker Instance.
- If you select Create Instance, you must set the parameters as described in the following table.
Parameter Description Billing MethodThe pay-as-you-go and subscription billing methods are supported. If you select the subscription billing method, 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.
You can select multiple instance types. For more information, see Instance families.
The selected instance types are displayed.
Specify the number of worker nodes (ECS instances) to be created.Note Quantity can be set to 0. A professional managed Kubernetes cluster cannot contain worker nodes.
System DiskEnhanced SSDs, standard SSDs, and ultra disks are supported.Note
- You can select Enable Backup to back up disk data.
- If you select an enhanced SSD as the system disk, you can set a custom performance level for the 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 enable disk encryption and disk backup when you mount a data disk.
Operating SystemACK supports the following node operating systems:
- Alibaba Cloud Linux 2. This is the default operating system.
- CentOS 7.x
Note CentOS 8.x and later are not supported.
- 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.
- If you select Add Existing Instance, you must select Elastic Compute Service (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.
- If you select Create Instance, you must set the parameters as described in the following table.
- Configure advanced settings of the worker nodes.
Parameter Description Node ProtectionSpecify 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 ImageYou can select a custom image for your nodes. 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.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 for this feature to be enabled on your account.
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 PolicySet 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.
Add taints to the worker nodes in the ACK cluster.
- Set Worker Instance.
- 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 Advanced Ingress configurations.
Select a volume plug-in. FlexVolume and CSI are supported. An ACK cluster 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 cluster. For more information, see Storage management-FlexVolume and Storage management-CSI.
Specify whether to install the CloudMonitor agent. By default, Install CloudMonitor Agent on ECS Instance and Enable Prometheus Monitoring are selected. After the CloudMonitor agent is installed on ECS instance-based nodes, you can view monitoring data about the nodes in the CloudMonitor console.
Specify whether to enable Log Service. You can select an existing Log Service project or create one. By default, Enable Log Service is selected. When you create an application, you can enable Log Service through a few steps. For more information, see Collect log files from containers by using Log Service.
By default, Install node-problem-detector and Create Event Center is selected. You can also specify whether to create Ingress dashboards in the Log Service console.
Workflow EngineSpecify whether to enable Alibaba Cloud Genomics Service (AGS).Note To use this feature, 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.
- Click Next:Confirm Order.
- Read and accept Terms of Service, and click Create Cluster. Note It requires about 10 minutes to create an ACK cluster that contains multiple nodes.
- 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 log data of the cluster. To view detailed log data, 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.