Skip to content

Latest commit

 

History

History
81 lines (58 loc) · 3.01 KB

README.md

File metadata and controls

81 lines (58 loc) · 3.01 KB
Raw

Deploy

Multiple Azure Kubernetes Service (AKS) Clusters

This example demonstrates creating multiple Azure Kubernetes Service (AKS) clusters in different regions and with different node counts. Please see https://docs.microsoft.com/en-us/azure/aks/ for more information about AKS.

Prerequisites

Ensure you have downloaded and installed the Pulumi CLI.

We will be deploying to Azure, so you will need an Azure account. If you don't have an account, sign up for free here. Follow the instructions here to connect Pulumi to your Azure account.

Running the Example

Note: Due to an issue in the Azure Terraform Provider (https://github.com/terraform-providers/terraform-provider-azurerm/issues/1635) the creation of an Azure Service Principal, which is needed to create the Kubernetes cluster (see index.ts), is delayed and may not be available when the cluster is created. If you get a Service Principal not found error, as a work around, you should be able to run pulumi up again, at which time the Service Principal should have been created.

After cloning this repo, cd into it and run these commands.

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

    $ pulumi stack init dev

  2. Create a Python virtualenv, activate it, and install dependencies:

    This installs the dependent packages needed for our Pulumi program.

    $ python3 -m venv venv
$ source venv/bin/activate
$ pip3 install -r requirements.txt

  3. Set the required configuration variables for this program:

    $ pulumi config set azure:environment public
$ pulumi config set password --secret [your-cluster-password-here]
$ ssh-keygen -t rsa -f key.rsa
$ pulumi config set sshPublicKey < key.rsa.pub

  4. Deploy everything with the pulumi up command. This provisions all the Azure resources necessary, including an Active Directory service principal and AKS clusters:

    $ pulumi up

  5. After a couple minutes, your AKS clusters will be ready. The AKS cluster names will be printed as output variables once pulumi up completes.

    $ pulumi up
...

Outputs:
  + aksClusterNames: [
  +     [0]: "akscluster-east513be264"
  +     [1]: "akscluster-westece285c7"
    ]
...

  6. At this point, you have multiple AKS clusters running in different regions. Feel free to modify your program, and run pulumi up to redeploy changes. The Pulumi CLI automatically detects what has changed and makes the minimal edits necessary to accomplish these changes.

  7. Once you are done, you can destroy all of the resources, and the stack:

    $ pulumi destroy
$ pulumi stack rm