Day 45: Azure Kubernetes Service (AKS) Setup and Management - Help with Nautilus AKS Task: "AKS cluster 'devops-aks' is not in a running state"

KodeKloud Engineer
, , ,
#1

Hello everyone,

I just attempted the Nautilus DevOps task to prepare an AKS cluster, but my validation failed with the following message:

"AKS cluster 'devops-aks' is not in a running state. You may check your work again to see what went wrong."

Here were my task requirements:

Cluster Name: devops-aks

Kubernetes Version: 1.36.x

Location: Central US

Network Access: Private

Node pool size: Standard_D2s_v3 with Min: 1, Max: 2

Container Insights / Monitoring: Disabled

Here is the exact Azure CLI command I used in the Cloud Shell:
Bash

RESOURCE_GROUP=$(az group list --query “[0].name” -o tsv)

az aks create
–resource-group “$RESOURCE_GROUP”
–name devops-aks
–location centralus
–kubernetes-version 1.36.2
–enable-private-cluster
–nodepool-name agentpool
–node-vm-size Standard_D2s_v3
–enable-cluster-autoscaler
–min-count 1
–max-count 2
–node-count 1
–generate-ssh-keys

The terminal completed the command and returned the large JSON success block, but the validation still failed.

My Questions:

Did I miss a flag in my CLI command to disable monitoring completely?

Is it possible I just clicked the "Check" button too early before the nodes finished provisioning?

Was there a known capacity issue for D2s_v3 VMs in centralus today?

(I have attached my screenshots of the terminal output below).

Thank you in advance for the help!

#2

I wouldn’t recommend using CloudShell – you should use the terminal we supply for your commands, to make sure that the grader script has access to artifacts it wants to check. You also need to wait until the cluster is completely initialized, or the grader will emit an error.

#3

Looking at your general approach, I’d note this task requirement:

  1. Edit the agentpool Node pools (delete all other node pool if exists) and configure the cluster with the following properties:
  • Node size: D2s v3.
  • Minimum node count: 1.
  • Maximum node count: 2.

Your script likely needs to put “agentpool” into a correct state before you run “az aks create”, and you’ll need to wait (quite a while – maybe 15 minutes) for the cluster to be in an “Available” state.

BTW: if you want to post a script, PLEASE make sure you put it into a code block – your script was garbled by Discourse’s editor, and it took me a bit to find all the characters that were swapped :-(. I did find, however, that your script works, and the grader accepted it, once I figured out what was garbled and fixed it.