Container Service on Google Cloud
The Google Cloud Container Service template scaffolds a Pulumi project that deploys a containerized service to Google Cloud Run for serverless container execution, with the container image stored in Artifact Registry. The template ships with placeholder app content so the project deploys end to end out of the box.
Using this template#
To use this template to deploy your own container service, make sure you’ve installed Pulumi and configured your Google Cloud credentials, then create a new project using the template in the language of your choice:
TypeScript
Python
Go
C#
HCLmkdir my-container-service && cd my-container-servicepulumi new container-gcp-typescriptAlternatively, you can create and configure a new project with this template (container-gcp-typescript) in Pulumi Cloud.
mkdir my-container-service && cd my-container-servicepulumi new container-gcp-pythonAlternatively, you can create and configure a new project with this template (container-gcp-python) in Pulumi Cloud.
mkdir my-container-service && cd my-container-servicepulumi new container-gcp-goAlternatively, you can create and configure a new project with this template (container-gcp-go) in Pulumi Cloud.
mkdir my-container-service && cd my-container-servicepulumi new container-gcp-csharpAlternatively, you can create and configure a new project with this template (container-gcp-csharp) in Pulumi Cloud.
mkdir my-container-service && cd my-container-servicepulumi new container-gcp-hclAlternatively, you can create and configure a new project with this template (container-gcp-hcl) in Pulumi Cloud.
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 index.tsindex.js__main__.pymain.goProgram.csProgram.fsProgram.vbApp.javaPulumi.yaml for a closer look.
Deploying the project#
You must supply an existing Google Cloud project ID and choose a region before deploying the container service. You can input both through the new-project wizard. Once the project is created, you can deploy it with pulumi up:
You must supply an existing Google Cloud project ID and choose a region before deploying the container service. You can input both through the new-project wizard. Once the project is created, you can deploy it with pulumi up:
You must supply an existing Google Cloud project ID and choose a region before deploying the container service. You can input both through the new-project wizard. Once the project is created, you can deploy it with pulumi up:
You must supply an existing Google Cloud project ID and choose a region before deploying the container service. You can input both through the new-project wizard. Once the project is created, you can deploy it with pulumi up:
The template deploys into your active Google Cloud project (read from your gcloud credentials) and defaults to the us-central1 region, which you can change with the region setting. Once the new project is created, you can deploy it with pulumi up:
pulumi upWhen the deployment completes, Pulumi exports the following stack output values:
- url
The HTTP URL of your Cloud Run service.
Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed url, for example, can be used from the command line to open the newly deployed container in your favorite web browser:
open $(pulumi stack output url)Customizing the project#
Projects created with the Container Service template expose the following configuration settings:
- containerPort
The port mapping for the container service. Defaults to port
8080.- cpu
The amount of CPU to allocate to each container instance. Defaults to
1CPU.- memory
The amount of memory to allocate to each container instance. Defaults to
1Gi.- concurrency
The maximum number of concurrent requests per container instance. Defaults to
50.- imageName
The name of the container image deployed to your Cloud Run service. Defaults to
my-app.- appPath
The location of the Dockerfile used to build the container image. Defaults to the
appfolder, which contains a “Hello World” example app.
- containerPort
The port mapping for the container service. Defaults to port
8080.- cpu
The amount of CPU to allocate to each container instance. Defaults to
1CPU.- memory
The amount of memory to allocate to each container instance. Defaults to
1Gi.- concurrency
The maximum number of concurrent requests per container instance. Defaults to
50.- imageName
The name of the container image deployed to your Cloud Run service. Defaults to
my-app.- appPath
The location of the Dockerfile used to build the container image. Defaults to the
appfolder, which contains a “Hello World” example app.
- containerPort
The port mapping for the container service. Defaults to port
8080.- cpu
The amount of CPU to allocate to each container instance. Defaults to
1CPU.- memory
The amount of memory to allocate to each container instance. Defaults to
1Gi.- concurrency
The maximum number of concurrent requests per container instance. Defaults to
50.- imageName
The name of the container image deployed to your Cloud Run service. Defaults to
my-app.- appPath
The location of the Dockerfile used to build the container image. Defaults to the
appfolder, which contains a “Hello World” example app.
- containerPort
The port mapping for the container service. Defaults to port
8080.- cpu
The amount of CPU to allocate to each container instance. Defaults to
1CPU.- memory
The amount of memory to allocate to each container instance. Defaults to
1Gi.- concurrency
The maximum number of concurrent requests per container instance. Defaults to
50.- imageName
The name of the container image deployed to your Cloud Run service. Defaults to
my-app.- appPath
The location of the Dockerfile used to build the container image. Defaults to the
appfolder, which contains a “Hello World” example app.
- region
The Google Cloud region to deploy into. Defaults to
us-central1.- image_name
The name of the container image deployed to your Cloud Run service. Defaults to
my-app.- app_path
The location of the Dockerfile used to build the container image. Defaults to the
appfolder, which contains a “Hello World” example app.- container_port
The port mapping for the container service. Defaults to port
8080.- cpu
The amount of CPU to allocate to each container instance. Defaults to
1CPU.- memory
The amount of memory to allocate to each container instance. Defaults to
1Gi.- concurrency
The maximum number of concurrent requests per container instance. Defaults to
80.
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:
pulumi config set containerPort 3000pulumi uppulumi config set containerPort 3000pulumi uppulumi config set containerPort 3000pulumi uppulumi config set containerPort 3000pulumi uppulumi config set container_port 3000pulumi upCleaning up#
You can cleanly destroy the stack and all of its infrastructure with pulumi destroy:
pulumi destroyLearn more#
- Browse other architecture templates in the Templates gallery.
- Explore the Google Cloud provider API docs in the Pulumi Registry.
- Walk through Pulumi from the ground up in Pulumi Tutorials.
- Read the latest container posts on the Pulumi blog.