To create an AKS cluster, complete the following steps:<\/p>\n\n\n\n
- Firstly, On the Azure portal menu or from the Home<\/strong> page, choose Create a resource<\/strong>.<\/li>
- choose Containers<\/strong> > Kubernetes Service<\/strong>.<\/li>
- On the Basics<\/strong> page, set the following options:
- Project details<\/strong>: choose an Azure Subscription<\/strong>, then choose or create an Azure Resource group<\/strong>, such as myResourceGroup<\/em>.<\/li>
- Cluster details<\/strong>: Enter a Kubernetes cluster name<\/strong>, such as myAKSCluster<\/em>. choose a Region<\/strong>, Kubernetes version<\/strong>, and DNS name prefix<\/strong> for the AKS cluster.<\/li>
- Primary node pool<\/strong>: choose a VM Node size<\/strong> for the AKS nodes. The VM size can’t<\/em> be changed once an AKS cluster has been deployed. – choose the number of nodes to deploy into the cluster. For this quickstart, set Node count<\/strong> to 1<\/em>. Node count can<\/em> be adjusted after the cluster has been deployed.<\/li><\/ul><\/li><\/ul>\n\n\n\n
![\"Create](\"https:\/\/docs.microsoft.com\/en-us\/azure\/aks\/media\/kubernetes-walkthrough-portal\/create-cluster-basics.png\")
Image Source – Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n - choose Next: Scale<\/strong> when complete.<\/li>
- On the Scale<\/strong> page, keep the default options. At the bottom of the screen,choose Next: Authentication<\/strong>.<\/li><\/ul>\n\n\n\n
- On the Authentication<\/strong> page, configure the following options:
- Create a new service principal by leaving the Service Principal<\/strong> field with (new) default service principal<\/strong>. Or you can choose Configure service principal<\/em> to use an existing one. If you use an existing one, you will need to provide the SPN client ID and secret.<\/li>
- Enable the option for Kubernetes role-based access controls (RBAC). This will provide more fine-grained control over access to the Kubernetes resources deployed in your AKS cluster.<\/li><\/ul>Alternatively, you can use a managed identity instead of a service principal. See use managed identities<\/a> for more information.<\/li><\/ol>\n\n\n\n
By default, Basic<\/em> networking is used, and Azure Monitor for containers is enabled. Click Review + create<\/strong> and then Create<\/strong> when validation completes.<\/p>\n\n\n\n
It takes a few minutes to create the AKS cluster. When your deployment is complete, click Go to resource<\/strong>, or browse to the AKS cluster resource group, such as myResourceGroup<\/em>, and select the AKS resource, such as myAKSCluster<\/em>.<\/p>\n\n\n\n
Connect to the cluster<\/strong><\/h3>\n\n\n\n
To manage a Kubernetes cluster, you use kubectl, the Kubernetes command-line client. The
kubectl<\/code> client is pre-installed in the Azure Cloud Shell.<\/p>\n\n\n\nOpen Cloud Shell using the
>_<\/code> button on the top of the Azure portal.<\/p>\n\n\n\n![\"Open](\"https:\/\/docs.microsoft.com\/en-us\/azure\/aks\/media\/kubernetes-walkthrough-portal\/aks-cloud-shell.png\")
Image Source – Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n To configure
kubectl<\/code> to connect to your Kubernetes cluster, use the az aks get-credentials<\/a> command. This command downloads credentials and configures the Kubernetes CLI to use them.<\/p>\n\n\n\nTo verify the connection to your cluster, use the kubectl get<\/a> command to return a list of the cluster nodes.<\/p>\n\n\n\n
Monitor health and logs<\/strong><\/h3>\n\n\n\n
When you created the cluster, Azure Monitor for containers was enabled. This monitoring feature provides health metrics for both the AKS cluster and pods running on the cluster.<\/p>\n\n\n\n
It may take a few minutes for this data to populate in the Azure portal. To see current status, uptime, and resource usage for the Azure Vote pods, browse back to the AKS resource in the Azure portal, such as myAKSCluster<\/em>. You can then access the health status as follows:<\/p>\n\n\n\n
- Firstly, Under Monitoring<\/strong> on the left-hand side, choose Insights<\/strong><\/li>
- Also, Across the top, choose to + Add Filter<\/strong><\/li>
- Subsequently, Select Namespace<\/em> as the property, then choose <All but kube-system><\/em><\/li>
- Finally, Choose to view the Containers<\/strong>.<\/li><\/ol>\n\n\n\n
Delete cluster<\/strong><\/h3>\n\n\n\n
When the cluster is no longer needed, delete the cluster resource, which deletes all associated resources. This operation can be completed in the Azure portal by selecting the Delete<\/strong> button on the AKS cluster dashboard. Alternatively, the az aks delete<\/a> command can be used in the Cloud Shell:<\/p>\n\n\n\n
az aks delete –resource-group myResourceGroup –name myAKSCluster –no-wait<\/p>\n\n\n\n
- Also, Across the top, choose to + Add Filter<\/strong><\/li>
- Enable the option for Kubernetes role-based access controls (RBAC). This will provide more fine-grained control over access to the Kubernetes resources deployed in your AKS cluster.<\/li><\/ul>Alternatively, you can use a managed identity instead of a service principal. See use managed identities<\/a> for more information.<\/li><\/ol>\n\n\n\n
- Create a new service principal by leaving the Service Principal<\/strong> field with (new) default service principal<\/strong>. Or you can choose Configure service principal<\/em> to use an existing one. If you use an existing one, you will need to provide the SPN client ID and secret.<\/li>
- On the Scale<\/strong> page, keep the default options. At the bottom of the screen,choose Next: Authentication<\/strong>.<\/li><\/ul>\n\n\n\n
- Cluster details<\/strong>: Enter a Kubernetes cluster name<\/strong>, such as myAKSCluster<\/em>. choose a Region<\/strong>, Kubernetes version<\/strong>, and DNS name prefix<\/strong> for the AKS cluster.<\/li>
- choose Containers<\/strong> > Kubernetes Service<\/strong>.<\/li>
![\"free](\"https:\/\/www.testpreptraining.ai\/tutorial\/wp-content\/uploads\/2020\/07\/Untitled-design-5.png\")
<\/a><\/figure><\/div>\n\n\n\n