The Kubernetes Cluster template creates an infrastructure as code project in your favorite language and deploys a managed Kubernetes cluster to Google Cloud with Pulumi. The architecture includes a VPC network with a subnet and deploys a Google Kubernetes Engine (GKE) cluster that provides a managed Kubernetes control plane and a nodepool for the cluster. Kubernetes worker nodes are deployed with private IP addresses for improved security. The template gives you a working project out of the box that you can customize easily and extend to suit your needs.
Using this template
To use this template to deploy your own Kubernetes cluster, make sure you’ve installed Pulumi and configured your Google Cloud credentials, then create a new project using the template in your language of choice:
$ mkdir my-k8s-cluster && cd my-k8s-cluster $ pulumi new kubernetes-gcp-typescript
$ mkdir my-k8s-cluster && cd my-k8s-cluster $ pulumi new kubernetes-gcp-python
$ mkdir my-k8s-cluster && cd my-k8s-cluster $ pulumi new kubernetes-gcp-go
$ mkdir my-k8s-cluster && cd my-k8s-cluster $ pulumi new kubernetes-gcp-csharp
$ mkdir my-k8s-cluster && cd my-k8s-cluster $ pulumi new kubernetes-gcp-yaml
Follow the prompts to complete the new-project wizard. When it’s done, you’ll have a complete Pulumi project that’s ready to deploy and configured with the most common settings. Feel free to inspect the code in
Deploying the project
You must supply an existing project ID to deploy the cluster. You can input the project ID through the new-project wizard. No additional configuration is required.
Once the new project is created, you can deploy it immediately with
$ pulumi up
When the deployment completes, Pulumi exports the following stack output values:
- The name of the virtual network containing the Kubernetes cluster resources.
- The unique ID of the virtual network containing the Kubernetes cluster resources.
- The name of the GKE cluster.
- The unique ID of the GKE cluster
- The cluster’s kubeconfig file which you can use with
kubectlto access and communicate with your clusters.
Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources.
Customizing the project
Projects created with the Kubernetes Cluster template expose the following configuration settings:
- The Google Cloud project ID to deploy into.
- The Google Cloud region to deploy into. Defaults to
- The desired number of nodes per zone in the nodepool. Defaults to
All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default,
Pulumi.dev.yaml) or by changing their values with
pulumi config set as shown below:
$ pulumi config set someProp ../some/value $ pulumi up
You can cleanly destroy the stack and all of its infrastructure with
$ pulumi destroy
Congratulations! You’re now well on your way to managing a production-grade Kubernetes cluster on Google Cloud with Pulumi — and there’s lots more you can do from here: