Day 35 - Azure for DevSecOps Operators#

Here is a summary of the steps to create an AKS cluster using Bicep:

1. Create a resource group:

   1
   az group create --name myResourceGroup --location eastus
   

2. Create a Bicep file (myAKS.bicep) with the following content:

   1
   param clusterName string = 'myAKSCluster'
   2
   param location string = 'eastus'
   3
   param dnsPrefix string = 'mydns'
   4
   param osDiskSizeInGB int = 30
   5
   param agentCount int = 1
   6
   param image string = 'CanonicalUbuntuServer'
   7
   
   8
   @landingSlot
   9
   resource aks myAKSCluster = Microsoft.ContainerInstances/managedClusters@2020-06-01 {
   10
      name: clusterName
   11
      location: location
   12
      properties: {
   13
         dnsPrefix: dnsPrefix
   14
         kubernetesVersion: '1.27.7'
   15
         osType: 'Linux'
   16
         servicePrincipalProfile: {
   17
            clientId: '<Your Service Principal Client ID>'
   18
            secret: '<Your Service Principal Secret>'
   19
         }
   20
         enableManagedIdentity: true
   21
      }
   22
      sku: {
   23
         tier: Premium
   24
         name: Standard_D4_v3
   25
      }
   26
      agentPoolProfiles: [
   27
         {
   28
            name: 'agentpool'
   29
            count: agentCount
   30
            osType: 'Linux'
   31
            osDiskSizeInGB: osDiskSizeInGB
   32
            vmSize: 'Standard_DS2_v3'
   33
            type: 'VirtualMachineScaleSets'
   34
            mode: System
   35
         }
   36
      ]
   37
   }
   

3. Install the Azure CLI and Azure PowerShell, if you haven’t already.

4. Run the following command to login to your Azure account:

   1
   az login
   

5. Deploy the Bicep file using the following command:

   1
   az bicep build myAKS.bicep --output-file aksDeployment.json
   2
   az deployment group create --name myAKSDeployment --resource-group myResourceGroup --template-file aksDeployment.json
   

6. Once the deployment is complete, you can connect to the AKS cluster using kubectl and az aks get-credentials.

7. You can also view the status of your AKS cluster in the Azure portal under “Kubernetes service” > “Clusters”.

This content walks through a step-by-step guide on deploying an Azure Kubernetes Service (AKS) cluster using Bicep, a declarative infrastructure as code language developed by Microsoft. The purpose of this deployment is to create a test lab environment for testing and learning.

The video starts with creating a Resource Group in Azure using the Azure CLI tool, followed by generating and copying an SSH key. Then, it deploys a Bicep file to create the AKS cluster, including the necessary resources such as the Linux admin username and SSH RSA public key.

Once the deployment is complete, the video shows how to retrieve the credentials from the AKs cluster using the az aks get-credentials command. This allows the user to interact with the deployed resources and manage them through the Azure CLI or other tools.

The video also demonstrates how to use the kubectl command-line tool to verify that the deployment was successful, including checking the node pools, workloads, and virtual machine sizes.

Throughout the video, the author provides tips and suggestions for using Bicep and Azure Kubernetes Service, as well as promoting best practices for deploying and managing cloud-based infrastructure. The purpose of this content appears to be educational, with the goal of helping viewers learn about Azure Kubernetes Service and how to deploy it using Bicep.