In comparison to default K8S config, for M8S has some differences. These differences for Azure ARC are nicely written previously here and helped me to write the guide below.
I made short notes list for M8S deployment for Azure ARC
Pre-reqs
- Ubuntu VM host with SNAP and multipass installed
- Azure CLI installed on nmk8m1 (main node) and proper registrations done on subscription
multipass launch -n nmk8m1 -c 4 -m 6gb -d 20gb
multipass launch -n nmk8w1 -c 2 -m 2gb -d 5gb
multipass launch -n nmk8w2 -c 2 -m 2gb -d 5gb
multipass shell nmk8m1
# on API server
microk8s enable dns storage helm
sudo usermod -a -G microk8s $USER
sudo chown -f -R $USER ~/.kube
microk8s config >> ~/.kube/config
microk8s add-node
# On each node run the installation and join node
sudo snap install microk8s --classic --channel=1.21
microk8s join 10.12.57.169:25000/c41265a169c27fc2ca12944693b97fd3/21bb78fa3d63
# on main node
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
az extension add -n connectedk8s
az account set --subscription "Microsoft Azure Sponsorship"
alias kubectl='microk8s kubectl'
microk8s config >> $HOME/.kube/config
kubectl config get-contexts
kubectl config use-context microk8s
# use existing group or create new one before using the command below
az connectedk8s connect -n AzureArcTestK8s -g AzureArcTest
az k8s-extension create --cluster-type connectedClusters --cluster-name AzureArcTestK8s --resource-group AzureArcTestK8s --extension-type Microsoft.PolicyInsights --name azurepolicy
0 comments on “MicroK8s notes on installation with Azure ARC”