Google Kubernetes Engine (GKE) Cluster
This example deploys a Google Cloud Platform (GCP) Google Kubernetes Engine (GKE) cluster and an application to it
Deploying the App
To deploy your infrastructure, follow the below steps.
Configure GCP Auth
$ gcloud auth login $ gcloud config set project <YOUR_GCP_PROJECT_HERE> $ gcloud auth application-default login
Note: This auth mechanism is meant for inner loop developer workflows. If you want to run this example in an unattended service account setting, such as in CI/CD, please follow instructions to configure your service account. The service account must have the role
Kubernetes Engine Admin/
After cloning this repo, from this working directory, run these commands:
Create a new Pulumi stack, which is an isolated deployment target for this example:
This will initialize the Pulumi program in Golang.
$ pulumi stack init
Set the required GCP configuration variables:
This sets configuration options and default values for our cluster.
$ pulumi config set gcp:project <YOUR_GCP_PROJECT_HERE> $ pulumi config set gcp:zone us-west1-a // any valid GCP Zone here
Stand up the GKE cluster:
To preview and deploy changes, run
pulumi updateand select “yes.”
updatesub-command shows a preview of the resources that will be created and prompts on whether to proceed with the deployment. Note that the stack itself is counted as a resource, though it does not correspond to a physical cloud resource.
You can also run
pulumi up --diffto see and inspect the diffs of the overall changes expected to take place.
pulumi upwill deploy the GKE cluster. Note, provisioning a new GKE cluster takes between 3-5 minutes.
$ pulumi update Previewing update (dev): Type Name Plan + pulumi:pulumi:Stack gcp-go-gke-dev create + └─ gcp:container:Cluster helloworld create Resources: + 2 to create Updating (dev): Type Name Plan + pulumi:pulumi:Stack gcp-go-gke-dev created + └─ gcp:container:Cluster helloworld created Outputs: ClusterName: "helloworld-9b9530f" KubeConfig : "<KUBECONFIG_CONTENTS>" Resources: + 2 created Duration: 3m3s
After 3-5 minutes, your cluster will be ready, and the kubeconfig JSON you’ll use to connect to the cluster will be available as an output.
Access the Kubernetes Cluster using
To access your new Kubernetes cluster using
kubectl, we need to setup the
kubeconfigfile and download
kubectl. We can leverage the Pulumi stack output in the CLI, as Pulumi facilitates exporting these objects for us.
$ pulumi stack output kubeconfig --show-secrets > kubeconfig $ export KUBECONFIG=$PWD/kubeconfig $ kubectl version $ kubectl cluster-info $ kubectl get nodes
Once you’ve finished experimenting, tear down your stack’s resources by destroying and removing it:
$ pulumi destroy --yes $ pulumi stack rm --yes