For information on setting up a production Kubernetes cluster on Azure please see Azure Kubernetes Service (AKS)

This script sets up a single-node Kubernetes development cluster on an Azure VM. While this is not intended to be a production cluster (AKS is a more complete solution). The approach is similar to using minkube or kind but it's a complete Kubernetes deployment using kubeadm.

We have found that the kubeadm approach helps engineers learn more about what is happening under the covers with Kubernetes and AKS and it's a great next step from minikube or kind. It is also a great way for developers to debug applications as they have full access to Kubernetes and can quickly experiment and debug. There are also potential cost savings as a developer can run a dedicated Kubernetes "cluster" on a single VM.

The scripts and instructions will work with other VM hosts with minimal changes

• Explanation of the steps in this script
• Kubernetes best practices
• Bootstrapping clusters with kubeadm
• Azure Kubernetes Service (AKS)

• Bash or Windows cmd shell
• Azure CLI (download)

Visual Studio Code Remote is highly recommended

• tested on Ubuntu 18.04 LTS
• minimum 2 cores with 2 GB RAM
• recommend 2 cores with 4 GB RAM

az account list -o table

# login to Azure (if necessary)
az login

# select subscription (if necesary)
az account set -s YourSubscriptionName

From a bash terminal

# change your resource group name and location if desired
export AKDC_LOC=centralus
export AKDC_RG=akdc

# Create a resource group
az group create -l $AKDC_LOC -n $AKDC_RG

# download setup script
# replace user name
curl https://raw.githubusercontent.com/microsoft/kubernetes-developer-cluster-kubeadm/main/scripts/akdc.sh > akdc.sh

# create an Ubuntu VM and install k8s
# save IP address into the AKDC_IP env var

export AKDC_IP=$(az vm create \
  -g $AKDC_RG \
  --admin-username akdc \
  -n akdc \
  --size standard_d2s_v3 \
  --image Canonical:UbuntuServer:18.04-LTS:latest \
  --os-disk-size-gb 128 \
  --generate-ssh-keys \
  --query publicIpAddress -o tsv \
  --custom-data akdc.sh)

echo $AKDC_IP

# delete SSH rule
az network nsg rule delete -g $AKDC_RG --nsg-name akdcNSG -o table --name default-allow-ssh

# For more security, replace --source-address-prefixes * with your IP or CIDR

# create SSH rule on port 2222
az network nsg rule create -g $AKDC_RG \
--nsg-name akdcNSG \
-n SSH2222 \
--description "SSH" \
--destination-port-ranges 2222 \
--protocol tcp \
--access allow \
--priority 1202 \
--source-address-prefixes *

# (optional) open NodePort range on NSG
az network nsg rule create -g $AKDC_RG \
--nsg-name akdcNSG --access allow \
--description "AKDC Ports" \
--destination-port-ranges 30000-32767 \
--protocol tcp \
-n AkdcPorts --priority 1200

# SSH into the VM
ssh akdc@${AKDC_IP} -p 2222

From a Windows cmd prompt

# change your resource group name and location if desired
set AKDC_LOC=centralus
set AKDC_RG=akdc

# Create a resource group
az group create -l %AKDC_LOC% -n %AKDC_RG%

# download setup script
curl https://raw.githubusercontent.com/microsoft/kubernetes-developer-cluster-kubeadm/main/scripts/akdc.sh > akdc.sh

# create an Ubuntu VM and install k8s
# save IP address into the AKDC_IP env var

for /f %f in (' ^
  az vm create ^
  -g %AKDC_RG% ^
  --admin-username akdc ^
  -n akdc ^
  --size standard_d2s_v3 ^
  --image Canonical:UbuntuServer:18.04-LTS:latest ^
  --os-disk-size-gb 128 ^
  --generate-ssh-keys ^
  --query publicIpAddress -o tsv ^
  --custom-data akdc.sh') ^
do set AKDC_IP=%f

echo %AKDC_IP%

# delete SSH rule
az network nsg rule delete -g %AKDC_RG% --nsg-name akdcNSG -o table --name default-allow-ssh

# For more security, replace --source-address-prefixes * with your IP or CIDR

# create SSH rule on port 2222
az network nsg rule create -g %AKDC_RG% ^
--nsg-name akdcNSG ^
-n SSH2222 ^
--description "SSH" ^
--destination-port-ranges 2222 ^
--protocol tcp ^
--access allow ^
--priority 1202 ^
--source-address-prefixes *

# (optional) open NodePort range on NSG
az network nsg rule create -g %AKDC_RG% ^
--nsg-name akdcNSG --access allow ^
--description "AKDC Ports" ^
--destination-port-ranges 30000-32767 ^
--protocol tcp ^
-n AkdcPorts --priority 1200

ssh akdc@%AKDC_IP% -p 2222

SSH into the VM first (instructions above)

# this will tell you when the user data script is complete
cat status

# your single-node k8s dev cluster is now ready
kubectl get all --all-namespaces

# (optional) install oh-my-bash kubectl aliases
sed -i "s/^plugins=($/plugins=(\n  kubectl/g" .bashrc
source .bashrc

# (optional) make sure everything is up to date
sudo apt update
sudo apt upgrade -y

# (optional) reboot if required
sudo shutdown -r now

You can usually reset your k8s cluster to a clean install with kubeadm reset If reset fails, you will need to delete the VM and create a new one.

From a bash shell in the VM via SSH

curl https://raw.githubusercontent.com/microsoft/kubernetes-developer-cluster-kubeadm/main/scripts/reset.sh > reset.sh
chmod +x reset.sh

# reset your cluster
./reset.sh

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Microsoft Contributor License Agreement.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

This project may contain trademarks or logos for projects, products, or services.

Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines.

Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.

Any use of third-party trademarks or logos are subject to those third-party's policies.