GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing docs.ctrlplane.dev — Quickstart - docs

This guide walks you through setting up a complete deployment pipeline with staging → production promotion and automated verification. By the end, you’ll have a working example of Ctrlplane’s core capabilities.

What You’ll Build

Deployment with automatic version creation from CI
Two environments (staging, production) with resource selectors
Verification that checks deployment health before promotion
Approval policy requiring sign-off for production

Prerequisites

Ctrlplane account (self-hosted)
API key (Settings → API Keys)
GitHub repository with CI workflow

Step 1: Create a System

A system groups related deployments. This is typically a product, platform, or bounded context.

Terraform

resource "ctrlplane_system" "quickstart" {
  name        = "Tutorial Quickstart"
  description = "A tutorial on how to use Ctrlplane found in the Quickstart guide."
}

Step 2: Register Resources

Resources are your deployment targets. In production, you’d sync these from Kubernetes or cloud providers. For this quickstart, we’ll create them manually.

# ctrlc apply -f resource.yaml
---
type: Resource
identifier: tutorial-quickstart-resource-staging
kind: KubernetesCluster
name: quickstart-staging-cluster
version: tutorial/quickstart/v1
metadata:
  tutorial: quickstart
  environment: staging
  region: us-east-1
config:
  number: 1
  string: "one"
  boolean: true
  array:
    - one
    - two
    - three
---
type: Resource
identifier: tutorial-quickstart-resource-production
kind: KubernetesCluster
name: quickstart-production-cluster
version: tutorial/quickstart/v1
metadata:
  tutorial: quickstart
  environment: production
  region: us-east-1
config:
  number: 1
  string: "one"
  boolean: true
  array:
    - one
    - two
    - three

resource "ctrlplane_resource" "quickstart_staging" {
  identifier = "tutorial-quickstart-resource-staging"
  kind       = "KubernetesCluster"
  name       = "quickstart-staging-cluster"
  version    = "tutorial/quickstart/v1"

  metadata = {
    tutorial    = "quickstart"
    environment = "staging"
    region      = "us-east-1"
  }

  config = {
    number  = 1
    string  = "one"
    boolean = true
    array   = ["one", "two", "three"]
  }
}

resource "ctrlplane_resource" "quickstart_production" {
  identifier = "tutorial-quickstart-resource-production"
  kind       = "KubernetesCluster"
  name       = "quickstart-production-cluster"
  version    = "tutorial/quickstart/v1"

  metadata = {
    tutorial    = "quickstart"
    environment = "production"
    region      = "us-east-1"
  }

  config = {
    number  = 1
    string  = "one"
    boolean = true
    array   = ["one", "two", "three"]
  }
}

ctrlc apply -f https://raw.githubusercontent.com/ctrlplanedev/ctrlplane/main/examples/quickstart/2-resources.yaml

Step 3: Create Environments

Environments use selectors to dynamically match resources. When you add new clusters with matching metadata, they’re automatically included.

Terraform

resource "ctrlplane_environment" "staging" {
  name              = "Staging"
  description       = "Pre-production validation"
  resource_selector = "resource.metadata['environment'] == 'staging'"
}

resource "ctrlplane_environment" "production" {
  name              = "Production"
  description       = "Live production environment"
  resource_selector = "resource.metadata['environment'] == 'production'"
}

Step 4: Create a Job Agent

Job agents execute your deployments. We’ll use a simple test runner, but Ctrlplane supports GitHub Actions, Kubernetes jobs, ArgoCD, or custom agents.

Terraform

resource "ctrlplane_job_agent" "quickstart" {
  name        = "Tutorial Quickstart Job Agent"
  description = "A tutorial on how to use Ctrlplane found in the Quickstart guide."

  test_runner {
    sleep = "5s"
  }
}

ctrlc apply -f https://raw.githubusercontent.com/ctrlplanedev/ctrlplane/main/examples/quickstart/4-job-agent.yaml

Step 5: Create a Deployment

A deployment represents your application. The job agent config tells Ctrlplane how to trigger deployments.

Terraform

# Production environment
resource "ctrlplane_deployment" "quickstart" {
  name        = "Tutorial Quickstart Deployment"
  description = "A tutorial on how to use Ctrlplane found in the Quickstart guide."

  job_agent {
    id = ctrlplane_job_agent.quickstart.id
  }
}

Step 6: Add Deployment Workflow

Create .github/workflows/deploy.yml in your repository:

name: Deploy

on:
  workflow_dispatch:
    inputs:
      job_id:
        description: "Ctrlplane Job ID"
        required: true

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Get deployment context
        uses: ctrlplanedev/get-job-inputs@v1
        id: job
        with:
          job_id: ${{ inputs.job_id }}
          api_key: ${{ secrets.CTRLPLANE_API_KEY }}

      - name: Deploy to Kubernetes
        run: |
          echo "Deploying ${{ steps.job.outputs.version_tag }}"
          echo "Environment: ${{ steps.job.outputs.environment_name }}"
          echo "Cluster: ${{ steps.job.outputs.resource_identifier }}"

          # Your deployment logic here
          # kubectl set image deployment/api-gateway \
          #   api-gateway=${{ steps.job.outputs.version_tag }}

Add CTRLPLANE_API_KEY to your repository secrets.

Step 7: Integrate CI Build

Add version creation to your build workflow (.github/workflows/build.yml):

- name: Install Ctrlplane CLI
  uses: ctrlplanedev/cli@main
  with:
    api_key: ${{ secrets.CTRLPLANE_API_KEY }}

- name: Create deployment version
  if: github.ref == 'refs/heads/main'
  run: |
    ctrlc api upsert version \
      --workspace <your-workspace> \
      --deployment ${{ secrets.CTRLPLANE_DEPLOYMENT_ID }}  \
      --tag ${{ github.sha }} \
      --name "${{ github.sha::7 }}" \
      --metadata github/owner=${{ github.repository_owner }} \
      --metadata github/repo=${{ github.event.repository.name }} \
      --metadata git/sha=${{ github.sha }} \
      --metadata git/branch=${{ github.ref_name }} \
      --metadata github/run-number=${{ github.run_number }} \
      --metadata github/run-id=${{ github.run_id }} \
      --metadata github/run-attempt=${{ github.run_attempt }}

Step 8: Add Production Approval

Create a policy requiring approval before production deployments

Terraform

resource "ctrlplane_policy" "production_approval" {
  name        = "Production Approval Policy"
  description = "Production Approval Policy"

  selector {
    environments = "environment.metadata['requires-approval'] == 'true'"
  }

  approval {
    required = 1
  }
}

Step 9: Test the Pipeline

Push a commit to main
CI builds and creates a version in Ctrlplane
Ctrlplane creates releases for staging and production
Staging deployment executes immediately
Verification runs health checks
Production waits for approval
After approval, production deploys and verifies

View the pipeline in the Ctrlplane UI:

Deployments → See version progression across environments
Releases → Track release progression across environments
Jobs → View execution details and logs

What You’ve Built

✅ Deployment orchestration with automatic environment progression
✅ Resource inventory with metadata-based environment selectors
✅ Verification ensuring deployment health before promotion
✅ Policy gates requiring approval for production

Next Steps

Policies

Configure gradual rollouts, concurrency limits, and custom gates

Verification

Add Datadog metrics, custom HTTP checks, and more

Resources

Sync resources from Kubernetes, AWS, or custom providers

Job Agents

Deploy with GitHub Actions, ArgoCD, or custom agents

Troubleshooting

Jobs not being created:

Verify resource metadata matches environment selectors
Check deployment has a job agent configured
Review policy denials in the Releases view

Verification failing:

Test the health endpoint manually
Check the success condition syntax
Review measurement data in the verification details

GitHub workflow not triggering:

Ensure job agent type is github
Verify workflow filename matches jobAgentConfig
Check GitHub App permissions

Need help? GitHub Discussions

Was this page helpful?

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.

GeezerVison

​What You’ll Build

​Prerequisites

​Step 1: Create a System

​Step 2: Register Resources

​Step 3: Create Environments

​Step 4: Create a Job Agent

​Step 5: Create a Deployment

​Step 6: Add Deployment Workflow

​Step 7: Integrate CI Build

​Step 8: Add Production Approval

​Step 9: Test the Pipeline

​What You’ve Built

​Next Steps

Policies

Verification

Resources

Job Agents

​Troubleshooting

What You’ll Build

Prerequisites

Step 1: Create a System

Step 2: Register Resources

Step 3: Create Environments

Step 4: Create a Job Agent

Step 5: Create a Deployment

Step 6: Add Deployment Workflow

Step 7: Integrate CI Build

Step 8: Add Production Approval

Step 9: Test the Pipeline

What You’ve Built

Next Steps

Troubleshooting