Get Started
Deploy your first application. Each change to your infrastructure is a manifest in a Git repository. Each manifest arrives as a pull request. You do not use the Google Cloud console.
- Create a ReleaseTrack: the path that your versions follow from development to production.
- Create an ApplicationSet: a group of applications that release together.
- Create an ExternalApplication. It names a trusted repository, an image, a project and a target.
- Create a DeploymentConfig for an environment. Its metadata.name matches the ExternalApplication.
- Commit the manifests and open a pull request.
- The platform posts a plan as a comment on the pull request.
- Merge. Infrastream applies the change and deploys the application to the development environment.
Choose how manifests reach the repository
A person or an agent can write the manifests. Each way gives the same result: a pull request with a plan of what will change. A colleague or an agent can review the pull request. Your repository branch rules decide if a review must happen.
| Way | Who uses it | What happens | Status |
|---|---|---|---|
| Beck, the assistant in the portal | Employees of your organization | You describe the change in plain words. Beck writes the manifests and opens the pull request. | Available |
| MCP, from your own AI tool | Developers and engineers | The AI tool signs in as you. Its tool write_pr writes the manifests to a feature branch as a pull request. | Pilot. Customers cannot use it yet. |
| By hand | Anyone with access to the manifest repository | You write the manifests, commit them and open the pull request. The steps below show how. | Available |
Beck and the MCP do not merge a change to production. In integration, an agent merge is planned (see the MCP Workflows Playbook). A person merges a pull request to production. Read Using Beck and The Agent Path.
Prerequisites
- A container image in a container registry.
- An
ExternalRegistrymanifest and aTrustedRepositorymanifest for the registry and the repository of the image. See Registries & Trust for samples. - The names of your
organization,organizational-unitandproject. - The manifest repository of your organization. Read Core Concepts for the kinds below.
Steps: write the manifests by hand
Beck and the MCP write the same manifests. These steps show what a first pull request holds.
-
Create a
ReleaseTrack. It lists the environments, in order, that a version passes through.apiVersion: lowops.manifests.v1
kind: ReleaseTrack
metadata:
name: my-product-releasetrack
organizational-unit: your-ou
organization: your-org
spec:
releaseStages:
- environments: [development]
- environments: [staging]
- environments: [production] -
Create an
ApplicationSet. It groups applications that release together.apiVersion: lowops.manifests.v1
kind: ApplicationSet
metadata:
name: my-app-set
release-track: my-product-releasetrack
organizational-unit: your-ou
organization: your-org
spec:
description: "A logical grouping for my product's applications" -
Create an
ExternalApplication. It names the image that you already have.apiVersion: lowops.manifests.v1
kind: ExternalApplication
metadata:
name: my-new-app
application-set: my-app-set
release-track: my-product-releasetrack
organizational-unit: your-ou
organization: your-org
spec:
trustedRepository: my-trusted-repo # a TrustedRepository manifest
image: my-image # the image in that repository
project: your-project-name
target: CLOUD_RUN # or KUBERNETES, or COMPUTEIf
targetisKUBERNETES, setspec.clusterto the name of aKubernetesmanifest. Support for Google Kubernetes Engine (GKE) is in active development and not yet generally available. -
Create a
DeploymentConfigfor the first environment. Itsmetadata.namemust be the name of theExternalApplication.apiVersion: lowops.manifests.v1
kind: DeploymentConfig
metadata:
name: my-new-app
project: your-project-name
environment: development
organizational-unit: your-ou
organization: your-org
spec:
version: "1.0.0"
container:
env:
- name: DATABASE_URL
value: "your-dev-database-url"
scaling:
min: 1
max: 5 -
Commit the manifests and open a pull request.
-
Read the plan that the platform posts as a comment on the pull request.
-
Merge the pull request. The engine applies the plan and deploys to
development.
Verify
The run for your merge shows the application as created. The output of the deployment run gives the URL of the service.
Your repository branch rules decide if a review must happen before the merge. Organization admins can bypass those rules. Set them with care.
Next
- Deploy an Application: choose between an
Applicationand anExternalApplication. - Set Up a Repository and CI: build the image on the platform, and use an
Applicationinstead of anExternalApplication. - Set Up a Custom Domain