Azure Kubernetes Service (AKS) cluster and Helm chart

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-cs-aks-helm
$ cd pulumi-examples/azure-cs-aks-helm

This example demonstrates creating an Azure Kubernetes Service (AKS) cluster and deploying a Helm Chart from Bitnami Helm chart repository into this cluster, all in one Pulumi program.

The example showcases the native Azure provider for Pulumi.

Prerequisites#

1. Install Pulumi
2. Configure Azure credentials
3. Install .NET

Deploying the example#

This example provisions a Kubernetes cluster running a public Apache web server, then verifies that you can access it.

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

   pulumi stack init dev

2. Set the Azure region location to use:

   pulumi config set azure-native:location westus2

3. Deploy everything with the pulumi up command. This provisions all the Azure resources necessary, including an Active Directory service principal, AKS cluster, and then deploys the Apache Helm Chart, all in a single gesture (takes 5-10 min):

   pulumi up

4. Now your cluster and Apache server are ready. Several output variables are printed, including your cluster name (ClusterName), Kubernetes config (Kubeconfig) and server IP address (ApacheServiceIP).

   Using these output variables, you may access your Apache server:

   curl $(pulumi stack output ApacheServiceIP)

   <html><body><h1>It works!</h1></body></html>

   And you may also configure your kubectl client using the Kubeconfig configuration:

   pulumi stack output Kubeconfig --show-secrets > kubeconfig.yaml
   KUBECONFIG=./kubeconfig.yaml kubectl get service

   NAME           TYPE           CLUSTER-IP    EXTERNAL-IP   PORT(S)                      AGE
   apache-chart   LoadBalancer   10.0.58.153   20.51.80.30   80:32707/TCP,443:32495/TCP   3m23s
   kubernetes     ClusterIP      10.0.0.1      <none>        443/TCP                      21m

5. At this point, you have a running cluster. 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. This could be altering the existing chart, adding new Azure or Kubernetes resources, or anything, really.

Cleaning up#

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

pulumi destroy
pulumi stack rm
rm kubeconfig.yaml