🚀 Deploying Kubernetes

Deploying AKS and Kubernetes can be extremely complex, with many networking, compute and other aspects to consider. However for the purposes of this workshop, a default and basic cluster can be deployed very quickly.

🔨 AKS Cluster Deployment

The following commands can be used to quickly deploy an AKS cluster:

# Create Azure resource group
az group create --name $RES_GROUP --location $REGION

# Create cluster
az aks create --resource-group $RES_GROUP \
  --name $AKS_NAME \
  --location $REGION \
  --node-count 2 --node-vm-size Standard_B2ms \
  --kubernetes-version $KUBE_VERSION \
  --verbose \
  --no-ssh-key

In case you get an error when creating cluster, Version x.xx.x is not supported in this region run the following to get the supported Kubernetes versions

az aks get-versions --location $REGION -o table

And re-run the create cluster command with a supported version number.

This should take around 5 minutes to complete, and creates a new AKS cluster with the following characteristics:

• Two small B-Series Nodes in a single node pool. Nodes are what your workloads will be running on. This is about as small and cheap as you can go and still have cluster that is useful for learning and experimentation.
• Basic 'Kubenet' networking, which creates an Azure network and subnet etc for us. See docs if you wish to learn more about this topic
• Local cluster admin account, with RBAC enabled, this means we don't need to worry about setting up users or assigning roles etc.
• AKS provides a wide range of 'turn key' addons, e.g. monitoring, AAD integration, auto-scaling, GitOps etc, however we'll not be using these.
• The use of SSH keys is skipped with --no-ssh-key as they won't be needed.
• You may wish to change the size or number of nodes, however this clearly has cost implications.

The az aks create command has MANY options however you shouldn't need to change or add any options for this workshop.

🔌 Connect to the Cluster

To enable kubectl (and other tools) to access the cluster, run the following:

az aks get-credentials --name $AKS_NAME --resource-group $RES_GROUP

This will create Kubernetes config file in your home directory ~/.kube/config which is the default location, used by kubectl.

Now you can run some simple kubectl commands to validate the health and status of your cluster:

# Get all nodes in the cluster
kubectl get nodes

# Get all pods in the cluster
kubectl get pods --all-namespaces

Don't be alarmed by all the strangely named pods you see running in the 'kube-system' namespace. These are deployed by default by AKS and perform management & system tasks we don't need to worry about. You can still consider your cluster "empty" at this stage.

⏯️ Appendix - Stopping & Starting the Cluster

If you are concerned about the costs for running the cluster you can stop and start it at any time. This essentially stops the node VMs in Azure, meaning the costs for the cluster are greatly reduced.

# Stop the cluster
az aks stop --resource-group $RES_GROUP --name $AKS_NAME

# Start the cluster
az aks start --resource-group $RES_GROUP --name $AKS_NAME

Start and stop operations do take several minutes to complete, so typically you would perform them only at the start or end of the day.