Docs Home
Azure Kubernetes Service (AKS) Cluster and Helm Chart
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
Install Pulumi.
Install .NET Core
We will be deploying to Azure, so you will need an Azure account. If you do not have an account, sign up for free here.
Setup and authenticate the native Azure provider for Pulumi.
Running the Example
In this example we will provision a Kubernetes cluster running a public Apache web server, verify we can access it, and clean up when done.
Get the code:
$ git clone git@github.com:pulumi/examples.git $ cd examples/azure-cs-aks-helmRestore dependencies and build:
$ dotnet buildCreate a new stack, which is an isolated deployment target for this example:
$ pulumi stack initSet the required configuration variables for this program:
$ pulumi config set azure-native:location westus2Deploy everything with the
pulumi upcommand. 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 upNow your cluster and Apache server are ready. Several output variables will be 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
kubectlclient using theKubeconfigconfiguration:$ 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 21mAt this point, you have a running cluster. Feel free to modify your program, and run
pulumi upto 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.TIP: if you make changes to the example code outside of an IDE, run the C# compiler after every change:
$ dotnet buildOnce you are done, you can destroy all of the resources, and the stack:
$ pulumi destroy $ pulumi stack rm $ rm kubeconfig.yaml