Skip to main content

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.

The first deployment, in seven stepsFour manifests, then three steps in git. Step 1 is a ReleaseTrack. Step 2 is an ApplicationSet in that ReleaseTrack. Step 3 is an ExternalApplication in that ApplicationSet. Step 4 is a DeploymentConfig with the same name as the ExternalApplication. Step 5 is a commit and a pull request. In step 6 the platform posts a plan as a comment on the pull request. In step 7 you merge, and Infrastream applies the change and deploys the application to the development environment.Declare in the manifest repositoryReleaseTrackmy-product-releasetrack1ApplicationSetmy-app-set2ExternalApplicationmy-new-app3DeploymentConfigmy-new-app4Commit andopen a pull requestthe manifests,in the manifest repository5Plana plan commenton the pull request6Merge and applythe app runs in thedevelopment environment7same name
The first deployment, in seven stepsFour manifests, then three steps in git. Step 1 is a ReleaseTrack. Step 2 is an ApplicationSet in that ReleaseTrack. Step 3 is an ExternalApplication in that ApplicationSet. Step 4 is a DeploymentConfig with the same name as the ExternalApplication. Step 5 is a commit and a pull request. In step 6 the platform posts a plan as a comment on the pull request. In step 7 you merge, and Infrastream applies the change and deploys the application to the development environment.Declare in the manifest repositoryReleaseTrackmy-product-releasetrack1ApplicationSetmy-app-set2ExternalApplicationmy-new-app3DeploymentConfigmy-new-app4Commit and open a pull requestthe manifests, in the manifest repository5Plana plan comment on the pull request6Merge and applythe app runs in the development environment7same name
  1. Create a ReleaseTrack: the path that your versions follow from development to production.
  2. Create an ApplicationSet: a group of applications that release together.
  3. Create an ExternalApplication. It names a trusted repository, an image, a project and a target.
  4. Create a DeploymentConfig for an environment. Its metadata.name matches the ExternalApplication.
  5. Commit the manifests and open a pull request.
  6. The platform posts a plan as a comment on the pull request.
  7. 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.

WayWho uses itWhat happensStatus
Beck, the assistant in the portalEmployees of your organizationYou describe the change in plain words. Beck writes the manifests and opens the pull request.Available
MCP, from your own AI toolDevelopers and engineersThe 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 handAnyone with access to the manifest repositoryYou 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 ExternalRegistry manifest and a TrustedRepository manifest for the registry and the repository of the image. See Registries & Trust for samples.
  • The names of your organization, organizational-unit and project.
  • 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.

  1. 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]
  2. 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"
  3. 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 COMPUTE

    If target is KUBERNETES, set spec.cluster to the name of a Kubernetes manifest. Support for Google Kubernetes Engine (GKE) is in active development and not yet generally available.

  4. Create a DeploymentConfig for the first environment. Its metadata.name must be the name of the ExternalApplication.

    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
  5. Commit the manifests and open a pull request.

  6. Read the plan that the platform posts as a comment on the pull request.

  7. 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​