Create Azure AKS Cluster
Azure Kubernetes Service (AKS) simplifies the process of deploying managed Kubernetes clusters in Azure by offloading operational overhead to Azure. As a managed Kubernetes service, Azure automatically handles critical tasks such as health monitoring and maintenance. For more information about Azure AKS clusters, please refer to the official documentation .
By using this guide, you can quickly start a Kubernetes cluster in your Azure account.
Preparation
Install a plugin
Before installation, you need to install the Azure AKS Cluster Management Component with one click on the global plugin tab.
Create Service Principal
This platform requires setting up a service principal and adding its role-based access permissions from the Azure portal. This is necessary to create and manage your Kubernetes cluster in AKS.
Tip: Azure Active Directory (AD) is used to dynamically create and manage other Azure resources, providing credentials for communication with AKS. For more information about service principals, please refer to the official AKS documentation .
-
Go to the Microsoft Azure portal homepage .
-
Click on Azure Active Directory.
-
Click on App registrations > New registration.
-
Enter the name of the service principal.
-
Under the Supported Account Types, select the corresponding account to use the service principal, and click Register.
-
After registration, you will be redirected to the application details page. Please copy and save the Application (Client) ID and Directory (Tenant) ID.
-
On the left navigation bar, click on Certificates & Secrets.
-
Click on New Client Secret.
-
Enter a brief description, select an expiration time, and click Add. Please copy and save the password in the Value field.
Assign Access Permission for Service Principal
-
Click on All Services in the left navigation bar.
-
Click on Subscribe.
-
Please copy and save the Subscription ID that will be associated with the Kubernetes cluster, and click on the Subscription Name.
-
Click on Access Control (Identity and Access Management).
-
Click Add > Add Custom Role.
-
In the JSON tab, click here to download the permission JSON file and replace the
permissionsfield in the example. -
On the Members tab, select User, group, or service principal in the Assign access to section, and choose the application registered in the Create Service Principal step as the service principal.
-
Click Save and your service principal now has access to AKS.
-
Based on the information obtained in the above steps, create cloud credentials on this platform.
Create Cluster - Basic Info
-
In the left navigation pane, click Clusters > Cluster of clusters.
-
Click on Create a cluster on the right side of the page
> Create AWS EKS Cluster.
| Parameter | Description |
|---|---|
| Cloud Credential | Select an existing cloud credential or create a cloud credential and use it. |
Create Cluster - AKS Cluster Settings
Cluster Settings
| Parameter | Description |
|---|---|
| Region | Please select the Azure region where this cluster is located. For more information, please refer to the official documentation . |
Network Settings
| Parameter | Description |
|---|---|
| Network Type | - kubenet: This plugin is the default configuration for AKS-created clusters. When using kubenet, each node in the cluster receives a routable IP address. Pods communicate with resources outside the AKS cluster using NAT. This approach reduces the number of IP addresses needed to be reserved for Pods in the network space. For more information, please refer to the
official documentation
. - Azure CNI: Pods can use a full virtual network connection and can be accessed directly from the connected network using the Pod’s private IP address. This plugin requires more IP address space. For parameter configuration information, please refer to the Plan cluster IP addresses section in the official documentation . |
| Authorized IP Range | The Kubernetes API server is the core of the Kubernetes control plane and the most important way to interact with and manage the cluster. To improve the security of the cluster and minimize the risk of attacks, it is recommended to restrict the IP address range that can access the API server. For more information, please refer to the official documentation . |
Add Node Pool
A node pool is a collection of nodes, such as high-performance and on-demand billing node pools. You can add various types of nodes to meet the requirements of different application scenarios.
-
Add one or more node pools.
Parameter Description Availability Zone Refers to the physical location within an Azure region. Availability zones are a feature that provides high availability by distributing virtual machines across one or more data centers to protect applications from hardware failures or planned maintenance events. Virtual Machine Size The instance type used for the virtual machine nodes in the node pool, based on the selected region and availability zone. For more information, please refer to the official documentation . Maximum Pods per Node The maximum number of pods that can be hosted on a single node. Scaling Method The method used for scaling nodes, either manual or automatic. If automatic scaling is chosen, please refer to the official documentation for detailed scaling strategies. Node Count/Node Count Range - Scaling Mode - Manual: Manually input the desired node count and update it manually after creation to achieve node scaling.
- Scaling Mode - Automatic: Provide a range for automatic node scaling to achieve node scaling automatically.Kubernetes Labels Labels are key-value pairs attached to nodes and can be used to define the attributes of the nodes. Taints Taints are a property of nodes that allow nodes to reject running certain pods or even evict pods. -
Click Create to view the progress of cluster creation.
Relevant operations
You can click the
on the right side of the cluster on the list page or click Actions in the upper right corner on the details page to update the resource configuration of the nodes under the cluster or delete the cluster that is no longer in use as needed.
| Operation | Description |
|---|---|
| Update | Update the created cluster configuration in Update Public Cloud Cluster Configuration, and the updated configuration will take effect in AKS simultaneously. |
| Delete | When deleting a cluster, the resources in AKS nodes will be released simultaneously. Please ensure that the applications in the projects associated with the cluster have been backed up or migrated before deletion. |