[Playground Series] How to create a managed Kubernetes cluster on Azure Playground?

Update - March 2024

The latest version of this guide can now be found here, and is where any future updates will be applied.


Hello guys, I saw many of you faced problems while trying to create an AKS instance in the playground, so I decided to write a post on that with step-by-step guidelines, check it out!

  1. Provision your Azure playground lab
    Prerequisite: Premium KodeKloud subscription.
    Access this link: Sign In | KodeKloud and click start lab to request a new Azure Playground instance, after a few seconds, you will receive your temp Azure portal account like the below image:

Access https://portal.azure.com using the provided account.

  1. Create Azure Kubernetes Service cluster

From the Azure portal dashboard, select Kubernetes Services or search for it in the search bar.

Then select “Create a Kubernetes cluster”

In the creation form, configure as below image

  • Resource group: select the pre-defined one
  • Cluster name: select any suitable name (kodekloud-demo)
  • Node size: Standard B2s
  • Scale Method: Manual
  • Node count: 2

Then click Next: Node pools and keep default configurations.

Then click Next: Access and keep default configurations.

Then click Next: Networking and keep default configurations.

Then click Next: Integrations, in this tab, make sure you disable the Container Monitoring

Then click Review + Create, wait for the final validation pass, then click Create to deploy your AKS instance.

It will take a few minutes for Azure to provision the necessary resource, take a cup of coffee and then enjoy your brand-new Kubernetes instance.

You may notice an error message in the red box like the below image, it expected issue in the Azure Playground and doesn’t impact any AKS’s features, so just ignored it.

When you click on the link Open Cloud Shell, you will be asked to create a storage account for the cloud shell, please follow the below steps to avoid the permission error (403).

From the above popup click “Show advanced settings” and complete the form as below image.

Subscription: leave the default value
Cloud Shell region: East US
Resource group: Use existing
Storage account: Create a new one (you need to pick a globally unique name)
File share: Create a new one (you need to pick a globally unique name)
As the name needs to be globally unique, you can use any random tool to generate a 24-character string with only lowercase char and number.
Then click CREATE STORAGE and wait for a few seconds, after created successfully, your Cloud Shell will appear to use.

Happy learning,
Trung.

Hi @trung-kodekloud,

Thanks for your instruction.

But I got error 403 when opening cloud shell and creating storage.

Please help!

Best regards,
Sergei

Hello @srjchsv,

I just updated the post to include the guideline for the Cloud Shell part, please follow it, and you will be able to provision your cluster.

Happy learning,
Trung.

@trung-kodekloud,

Finally deployed and connected via cloud shell. Thanks!

Sincerely,
Sergei

1 Like

Glad to hear that Sergei.

Thanks,
Trung.

@trung-kodekloud Really appreciate it, will do it from my side once and will update if face any issues.

Can you do the same for EKS and Google Kubernetes

1 Like

Yeah, I’m going to roll out more in the upcoming days/weeks.

1 Like

This one for Google Cloud (GKE).

  • Resource ‘kodekloud-demo’ was disallowed by policy. (Code: RequestDisallowedByPolicy)

I get above error , please assist

Please follow this guide to create an AKS cluster in the Azure Playground:
certified-kubernetes-administrator-course/managed-clusters/aks/console at master · kodekloudhub/certified-kubernetes-administrator-course (github.com)

hi guys.

i have been trying for hours to create an AKS cluster with no luck. i don’t know what i’m missing . i followed all the instructions that was provided from the link but still getting error.
help please.

Did you follow the guide directly above your post? I just followed it and it works fine.

Make sure you edit the nodepool correctly.