Container Service on Azure

The Container Service template creates an infrastructure as code project in your favorite language that deploys a container service to Azure. You can then use the container service to build your own containerized application. The architecture includes Azure Container Instances (ACI) for running containers on serverless compute and an Azure Container Registry that stores the container image. The template generates a complete infrastructure project with example app content, providing you with a working project out of the box that you can customize easily and extend to suit your needs.

An architecture diagram of the Pulumi Azure Container Service template

Using this template

To use this template to deploy your own container service, make sure you’ve installed Pulumi and configured your Azure credentials, then create a new project using the template in your language of choice:

$ mkdir my-container-service && cd my-container-service
$ pulumi new container-azure-typescript
$ mkdir my-container-service && cd my-container-service
$ pulumi new container-azure-python
$ mkdir my-container-service && cd my-container-service
$ pulumi new container-azure-go
$ mkdir my-container-service && cd my-container-service
$ pulumi new container-azure-csharp

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.js index.ts main.go Program.cs Program.fs Program.vb Pulumi.yaml for a closer look.

Deploying the project

The template requires no additional configuration. Once the new project is created, you can deploy it immediately with pulumi up:

$ pulumi up

When the deployment completes, Pulumi exports the following stack output values:

The hostname of the container group.
The public IP address of the container group.
The HTTP URL of the container group.

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 application 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:

The path to the folder containing the application and Dockerfile. Defaults to ./app, which contains a “Hello world” example.
The port to expose on the container. Defaults to 80.
The number of CPU cores to allocate on the container. Defaults to 1.
The amount of memory, in GB, to allocate on the container. Defaults to 2.
The name of the container image to be published to Azure Container Registry. Defaults to my-app.
The tag applied to published container images. Defaults to latest.

All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, or by changing their values with pulumi config set as shown below:

$ pulumi config set someProp ../some/value
$ pulumi up

Tidying up

You can cleanly destroy the stack and all of its infrastructure with pulumi destroy:

$ pulumi destroy

Learn more

Congratulations! You’re now well on your way to managing a production-grade container service on Azure with Pulumi — and there’s lots more you can do from here: