Skip to content

Latest commit

 

History

History
183 lines (132 loc) · 6.51 KB

creating-aks-cluster.md

File metadata and controls

183 lines (132 loc) · 6.51 KB
Raw

Create an AKS cluster

The following guide is based upon the repos from lastcoolnameleft and Azure Kubernetes Hackfest.

Goal: Create AKS cluster.

This workshop uses AKS cluster with Linux containers. To create a Windows Server container on an AKS cluster, consider exploring AKS documents. This cluster deployment utilizes Azure CLI v2.x from your local terminal or via Azure Cloud Shell. Instructions for installing Azure CLI can be found here.

Prerequisite Tasks

Follow the prequisite steps if you need to verify your Azure subscription.

  • Ensure you are using the correct Azure subscription you want to deploy AKS to.

     # View subscriptions
 az account list   

 # Verify selected subscription
 az account show
    # Set correct subscription (if needed)/
az account set --subscription <subscription_id>

# Verify correct subscription is now set
az account show

Steps

  1. Create a unique identifier suffix for resources to be created in this lab.

    UNIQUE_SUFFIX=$USER$RANDOM
# Remove Underscores and Dashes (Not Allowed in AKS and ACR Names)
UNIQUE_SUFFIX="${UNIQUE_SUFFIX//_}"
UNIQUE_SUFFIX="${UNIQUE_SUFFIX//-}"
# Check Unique Suffix Value (Should be No Underscores or Dashes)
echo $UNIQUE_SUFFIX
# Persist for Later Sessions in Case of Timeout
echo export UNIQUE_SUFFIX=$UNIQUE_SUFFIX >> ~/.bashrc

# For mac user, please replace the profile name if you use zsh.
echo export UNIQUE_SUFFIX=$UNIQUE_SUFFIX >> ~/.zshrc

    _ Note this value as it will be used in the next couple labs. _

  2. Create an Azure Resource Group in your chosen region. We will use East US in this example.

    # Set Resource Group Name using the unique suffix
RGNAME=aks-rg-$UNIQUE_SUFFIX
# Persist for Later Sessions in Case of Timeout
echo export RGNAME=$RGNAME >> ~/.bashrc
# Set Region (Location)
LOCATION=eastus
# Persist for Later Sessions in Case of Timeout
echo export LOCATION=eastus >> ~/.bashrc
# Create Resource Group
az group create -n $RGNAME -l $LOCATION

  3. Create your AKS cluster in the resource group created in step 2 with 3 nodes. We will check for a recent version of kubnernetes before proceeding. You will use the Service Principal information from the prerequisite tasks.

    Use Unique CLUSTERNAME

    # Set AKS Cluster Name
CLUSTERNAME=aks${UNIQUE_SUFFIX}
# Look at AKS Cluster Name for Future Reference
echo $CLUSTERNAME
# Persist for Later Sessions in Case of Timeout
echo export CLUSTERNAME=aks${UNIQUE_SUFFIX} >> ~/.bashrc

    Get available kubernetes versions for the region. You will likely see more recent versions in your lab.

    az aks get-versions -l $LOCATION --output table
    KubernetesVersion    Upgrades
-------------------  ------------------------
1.22.4               None available
1.22.2               1.22.4
1.21.7               1.22.2, 1.22.4
1.21.2               1.21.7, 1.22.2, 1.22.4
1.20.13              1.21.2, 1.21.7
1.20.9               1.20.13, 1.21.2, 1.21.7
1.19.13              1.20.9, 1.20.13
1.19.11              1.19.13, 1.20.9, 1.20.13

    For this lab we'll use 1.22.4

    K8SVERSION=1.22.4
echo export K8SVERSION=1.22.4 >> ~/.bashrc

    The below command can take 10-20 minutes to run as it is creating the AKS cluster. Please be PATIENT and grab a coffee/tea/kombucha...

    # Create AKS Cluster - it is important to set the network-plugin as azure in order to connec to Calico Cloud
az aks create -n $CLUSTERNAME -g $RGNAME \
--kubernetes-version $K8SVERSION \
--enable-managed-identity \
--node-count 3 \
--network-plugin azure \
--generate-ssh-keys \
--no-wait

  4. Verify your cluster status. The ProvisioningState should be Succeeded

    az aks list -o table -g $RGNAME
    Name         Location    ResourceGroup    KubernetesVersion    ProvisioningState    Fqdn
-----------  ----------  ---------------  -------------------  -------------------  -------------------------------------------------------------
aks-cc-test  eastus      aks-rg-jessie    1.22.4               Succeeded            aks-cc-tes-aks-rg-jessie-03cfb8-20425f88.hcp.eastus.azmk8s.io

  5. Get the Kubernetes config files for your new AKS cluster

    az aks get-credentials -n $CLUSTERNAME -g $RGNAME

  6. Verify you have API access to your new AKS cluster

    Note: It can take 5 minutes for your nodes to appear and be in READY state. You can run watch kubectl get nodes to monitor status. Otherwise, the cluster is ready when the output is similar to the following:

    kubectl get nodes
    NAME                                STATUS   ROLES   AGE     VERSION
aks-nodepool1-45823991-vmss000000   Ready    agent   2m22s   v1.22.4
aks-nodepool1-45823991-vmss000001   Ready    agent   2m24s   v1.22.4
aks-nodepool1-45823991-vmss000002   Ready    agent   2m26s   v1.22.4

    To see more details about your cluster:

    kubectl cluster-info

  7. Download this repo into your environment:

    git clone https://github.com/tigera-solutions/calicocloud-kaas-workshop-demo.git

cd calicocloud-kaas-workshop-demo

  8. [Optional] scale your node group as desired count.

    az aks nodepool scale --name <your-node-pool> --cluster-name $CLUSTERNAME -g $RGNAME --node-count 3

Next steps

You should now have a Kubernetes cluster running with 3 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.

➡️ Join the cluster to Calico Cloud

↩️ README.md - STEP 1 - Create a compatible k8s cluster