Azure Kubernetes Service (AKS) Cluster using the native Azure Provider

This example lives in the pulumi/examples repository. Check out just this directory to use it:

$ git clone --filter=blob:none --sparse https://github.com/pulumi/examples pulumi-examples
$ git -C pulumi-examples sparse-checkout set azure-py-aks
$ cd pulumi-examples/azure-py-aks

This example deploys an AKS cluster, creates an Azure Active AD application, creates a Service Principal and sets credentials to manage access to the cluster.

Deploying the App#

To deploy your infrastructure, follow the below steps.

Prerequisites#

1. Install Pulumi
2. Install Python 3.6 or higher
3. Configure Azure Credentials

Steps#

After cloning this repo, from this working directory, run these commands:

1. Create a new stack, which is an isolated deployment target for this example:

   $ pulumi stack init

2. Set the Azure region location to use:

   $ pulumi config set azure-native:location westus2

3. Initiate pulumi to stand up the cluster

   $ pulumi up

   Note: Due to a propagation delay in Azure AD, the Service Principal created for the cluster may not be available the moment the cluster is provisioned. If you get a “Service Principal not found” error, run pulumi up again and it should complete successfully.

4. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you’ll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:

   $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml

   Once you have this file in hand, you can interact with your new cluster as usual via kubectl:

   $ KUBECONFIG=./kubeconfig.yaml kubectl get nodes

5. From there, feel free to experiment. Simply making edits and running pulumi up will incrementally update your stack.

6. Once you’ve finished experimenting, tear down your stack’s resources by destroying and removing it:

   $ pulumi destroy --yes
   $ pulumi stack rm --yes