This topic describes how to create a managed 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 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.
- 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.
- To create an ACK cluster that runs 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 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.
Procedure
Result
- After the cluster is created, you can find 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.
-
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 connections 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 it. 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 it. We recommend that you do not perform operations on the cluster during the restart process.
- Bind EIP: You can select an existing EIP or create one.
- 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 name
is
<cluster_id>.<region_id>.alicontainer.com
.Note To rebind the domain name, click Rebind Domain Name.
- 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.
- You can use kubectl to connect to the cluster and run the
kubectl get node
command to query information about the nodes in the cluster. For more information, see Use kubectl to connect to an ACK cluster.