https://github.com/tigera-solutions/aks-workshop-prep
This repository will help you to build an AKS cluster using Azure Cloud Shell for Tigera's Calico Cloud workshop.
https://github.com/tigera-solutions/aks-workshop-prep
aks azure cc prep regismartins workshop
Last synced: 8 months ago
JSON representation
This repository will help you to build an AKS cluster using Azure Cloud Shell for Tigera's Calico Cloud workshop.
- Host: GitHub
- URL: https://github.com/tigera-solutions/aks-workshop-prep
- Owner: tigera-solutions
- Created: 2023-08-01T10:43:23.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-08-21T17:51:23.000Z (over 1 year ago)
- Last Synced: 2025-04-06T03:33:40.937Z (11 months ago)
- Topics: aks, azure, cc, prep, regismartins, workshop
- Homepage:
- Size: 29.3 KB
- Stars: 8
- Watchers: 1
- Forks: 6
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Calico Cloud on AKS - Workshop Environment Preparation
This repository will guide you through the preparation process of building an AKS cluster using the Azure Cloud Shell that will be used in Tigera's Calico Cloud workshop. The goal is to reduce the time used for setting up infrastructure during the workshop, optimizing the Calico Cloud learning and ensuring everyone is on the same page.
## Getting Started with Azure Cloud Shell
The following are the basic requirements to **start** the workshop.
* Azure Account [Azure Portal](https://portal.azure.com)
* Git [Git SCM](https://git-scm.com/downloads)
* Azure Cloud Shell [https://shell.azure.com](https://shell.azure.com)
* Azure AKS Cluster
# Instructions
1. Login to Azure Portal at http://portal.azure.com.
2. Open the Azure Cloud Shell and choose Bash Shell (do not choose Powershell)
3. The first time Cloud Shell is started will require you to create a storage account.
> Note: In the cloud shell, you are automatically logged into your Azure subscription.
4. [Optional] If you have more than one Azure subscription, ensure you are using the one you want to deploy AKS to.
View subscriptions
```bash
az account list
```
Verify selected subscription
```bash
az account show
```
Set correct subscription (if needed)
```bash
az account set --subscription
```
Verify correct subscription is now set
```bash
az account show
```
5. Configure the kubectl autocomplete.
```bash
source <(kubectl completion bash) && source /usr/share/bash-completion/bash_completion
echo "source <(kubectl completion bash)" >> ~/.bashrc
echo "source /usr/share/bash-completion/bash_completion" >> ~/.bashrc
```
You can also use a shorthand alias for kubectl that also works with completion:
```bash
alias k=kubectl
complete -o default -F __start_kubectl k
echo "alias k=kubectl" >> ~/.bashrc
echo "complete -o default -F __start_kubectl k" >> ~/.bashrc
```
6. [Optional] Instal k9s, if you like it.
```bash
curl --silent --location "https://github.com/derailed/k9s/releases/download/v0.32.3/k9s_Linux_amd64.tar.gz" | tar xz -C /tmp
mkdir -p ~/.local/bin
mv /tmp/k9s ~/.local/bin
k9s version
```
## Deploy an Azure AKS Cluster
1. Define the environment variables to be used by the resources definition.
> **NOTE**: In the following section, we'll create some environment variables. If your terminal session restarts, you may need to reset these variables. You can do that using the following command:
>
> ```console
> source ~/workshopvars.env
> ```
```bash
export RESOURCE_GROUP=tigera-workshop
export CLUSTERNAME=aks-workshop
export LOCATION=canadacentral
# Persist for later sessions in case of disconnection.
echo export RESOURCE_GROUP=$RESOURCE_GROUP > ~/workshopvars.env
echo export CLUSTERNAME=$CLUSTERNAME >> ~/workshopvars.env
echo export LOCATION=$LOCATION >> ~/workshopvars.env
```
2. If not created, create the Resource Group in the desired Region.
```bash
az group create \
--name $RESOURCE_GROUP \
--location $LOCATION
```
3. Create the AKS cluster with Azure CNI network plugin.
```bash
az aks create \
--resource-group $RESOURCE_GROUP \
--name $CLUSTERNAME \
--kubernetes-version 1.29 \
--location $LOCATION \
--node-count 2 \
--node-vm-size Standard_B2ms \
--max-pods 100 \
--generate-ssh-keys \
--network-plugin azure
```
4. Verify your cluster status. The `ProvisioningState` should be `Succeeded`
```bash
az aks list -o table | grep $CLUSTERNAME
```
You may get an output like the following:
WARNING: [Warning] This output may compromise security by showing the following secrets: keyData, ssh, linuxProfile, publicKeys. Learn more at: https://go.microsoft.com/fwlink/?linkid=2258669
aks-workshop canadacentral tigera-workshop 1.29 1.29.2 Succeeded aks-worksh-tigera-workshop-03cfb8-mllwb5a6.hcp.canadacentral.azmk8s.io
5. Get the credentials to connect to the cluster.
```bash
az aks get-credentials --resource-group $RESOURCE_GROUP --name $CLUSTERNAME
```
6. Verify you have API access to your new AKS cluster
```bash
kubectl get nodes
```
The output will be something similar to the this:
NAME STATUS ROLES AGE VERSION
aks-nodepool1-30304837-vmss000000 Ready 10m v1.29.2
aks-nodepool1-30304837-vmss000001 Ready 10m v1.29.2
To see more details about your cluster:
```bash
kubectl cluster-info
```
The output will be something similar to the this:
Kubernetes control plane is running at https://aks-zero-t-rg-zero-trust-wo-03cfb8-b3feb0f8.hcp.canadacentral.azmk8s.io:443
CoreDNS is running at https://aks-zero-t-rg-zero-trust-wo-03cfb8-b3feb0f8.hcp.canadacentral.azmk8s.io:443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://aks-zero-t-rg-zero-trust-wo-03cfb8-b3feb0f8.hcp.canadacentral.azmk8s.io:443/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
You should now have a Kubernetes cluster running with 2 nodes. You do not see the master servers for the cluster because these are managed by Microsoft. The Control Plane services which manage the Kubernetes cluster such as scheduling, API access, configuration data store and object controllers are all provided as services to the nodes.
7. Verify the settings required for Calico Cloud.
```bash
az aks show --resource-group $RESOURCE_GROUP --name $CLUSTERNAME --query 'networkProfile'
```
You should see "networkPlugin": "azure" and "networkPolicy": null (networkPolicy will just not show if it is null).
8. Verify the transparent mode by running the following command in one node
```bash
VMSSGROUP=$(az vmss list --output table | grep -i $RESOURCE_GROUP | grep -i $CLUSTERNAME | awk -F ' ' '{print $2}')
VMSSNAME=$(az vmss list --output table | grep -i $RESOURCE_GROUP | grep -i $CLUSTERNAME | awk -F ' ' '{print $1}')
az vmss run-command invoke -g $VMSSGROUP -n $VMSSNAME --scripts "cat /etc/cni/net.d/*" --command-id RunShellScript --instance-id 0 --query 'value[0].message' --output table
```
> output should contain "mode": "transparent"
9. Stop the Cluster until the workshop starts.
```bash
az aks stop --resource-group $RESOURCE_GROUP --name $CLUSTERNAME
```
10. To start your cluster when the workshop time has come use:
```bash
az aks start --resource-group $RESOURCE_GROUP --name $CLUSTERNAME
```