This example demonstrates creating an Azure Kubernetes Service (AKS) Cluster, and deploying a Helm Chart into it, all in one Pulumi program. Please see https://docs.microsoft.com/en-us/azure/aks/ for more information about AKS.
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.
This example deploys a Helm Chart from Bitnami's Helm chart repository, so you will need to install the Helm CLI and configure it:
$ helm init --client-only
$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm repo updateAfter cloning this repo, cd into it and run these commands. A Kubernetes cluster and Apache web server will appear!
-
Create a new stack, which is an isolated deployment target for this example:
$ pulumi stack init
-
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
-
Deploy 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:$ pulumi up
-
After a couple minutes, your cluster and Apache server will be ready. Three output variables will be printed, reflecting your cluster name (
cluster), Kubernetes config (kubeConfig) and server IP address (serviceIP).Using these output variables, you may
curlyour Apache server'sserviceIP:$ curl $(pulumi stack output serviceIP) <html><body><h1>It works!</h1></body></html>
And you may also configure your
kubectlclient using thekubeConfigconfiguration:$ pulumi stack output kubeConfig > kubeconfig.yaml $ KUBECONFIG=./kubeconfig.yaml kubectl get service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE apache-apache LoadBalancer 10.0.125.196 40.76.52.208 80:32080/TCP,443:31419/TCP 9m kubernetes ClusterIP 10.0.0.1 <none> 443/TCP 13h
-
At 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. -
Once you are done, you can destroy all of the resources, and the stack:
$ pulumi destroy $ pulumi stack rm
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent