Skip to content

Latest commit

 

History

History
79 lines (59 loc) · 2.41 KB

01-create-cluster.md

File metadata and controls

79 lines (59 loc) · 2.41 KB
Raw

Create an AKS Cluster

Create a resource group to hold the cluster. This resource group should be provisioned in East US.

az group create --name ignite18 --location eastus

Output:

{
  "id": "/subscriptions/57ac26cf-a9f0-4908-b300-9a4e9a0fb205/resourceGroups/foo",
  "location": "westus2",
  "managedBy": null,
  "name": "foo",
  "properties": {
    "provisioningState": "Succeeded"
  },
  "tags": null
}

Create a two node AKS cluster running Kubernetes 1.11:

az aks create -g ignite18 --name ignite18 \
    --kubernetes-version 1.11.2 \
    --node-count 2 \
    --enable-addons http_application_routing --no-ssh-key

This cluster create will provision the control plane and attach VMs to your cluster. Initial cluster creation usually takes about 15 minutes.

If you close your Cloud Shell instance, you can watch for cluster creation to complete:

watch az aks list -g ignite18 -o table

Remember: Press CTRL+C to stop watching.

Output:

Name      Location    ResourceGroup    KubernetesVersion    ProvisioningState    Fqdn
--------  ----------  ---------------  -------------------  -------------------  ------------------------------------------------------
ignite18  eastus      ignite18         1.11.2               Succeeded            ignite18-ignite18-57ac26-22b0f7a8.hcp.eastus.azmk8s.io

Fetch cluster credentials

Next, we need to fetch credentials to authenticate to the Kubernetes API. We will ask AKS for the cluster admin credentials so that we can configure Resource Based Access Control (RBAC) in a later step.

az aks get-credentials -g ignite18 -n ignite18 --admin

Output:

Merged "ignite18-admin" as current context in /Users/jhansen/.kube/config

List cluster nodes

Next, let's talk to the new cluster and list the cluster nodes:

kubectl get nodes

Note: you will notice that the only nodes you see are your agent nodes; that's because in this case AKS manages the master nodes for you. You can run this same command using ACS-engine, for example, and you will see all the nodes, master and agent.

Output:

NAME                                         STATUS    ROLES     AGE       VERSION
aks-nodepool1-25718494-0                     Ready     agent     1d        v1.11.2
aks-nodepool1-25718494-1                     Ready     agent     1d        v1.11.2

Next Let's deploy our services...