Skip to main content
Version: 0.5 (Next)

Pipeline Templates

Pipeline templates automatically configure CI/CD workflows for your applications, providing instant containerization, registry publishing, and multi-environment deployments.

How It Works

When you register an application, Konstruct automatically:

  1. Adds GitHub Actions workflows to your repository:

    • publish.yaml - Builds containers and publishes to ECR
    • deploy.yaml - Manages deployments across environments
  2. Creates Helm charts for Kubernetes deployments

  3. Configures multi-stage pipelines based on your environment configuration

Default Pipeline Features

The Konstruct default pipeline template provides:

Automated Container Building

  • Triggers on commits to main branch
  • Builds your Dockerfile automatically
  • Tags images with semantic versions
  • Pushes to your organization's AWS ECR registry

Helm Chart Management

  • Auto-generates Helm charts for your application
  • Versions charts alongside your application
  • Publishes charts to your organization's chart registry
  • Supports environment-specific values

Progressive Deployments

  • Deploys through your configured environment stages
  • Supports pre-release and release environments
  • Automatic rollout to all clusters in an environment
  • Built-in health checks and monitoring once deployed on the Applications page

Benefits

  • Zero Configuration - Works immediately after app registration
  • Best Practices Built-in - Security scanning, versioning, and GitOps
  • Consistency - All apps follow the same proven patterns
  • Customizable - Eject and customize for your needs

Common Use Cases

  • Standardize CI/CD across all applications
  • Implement progressive deployment strategies
  • Ensure consistent container and chart versioning
  • Enable GitOps workflows automatically

Getting Started

  1. Create your first pipeline template
  2. Apply templates to applications
  3. Browse upstream template examples to see what's available

Upstream Template Examples

Konstruct ships two pipeline ecosystems in konstructio/konstruct-templates:

  • Default — Simple publish + manual deploy. Two workflows, configurable environments.
  • Promotion — 4-environment progressive pipeline (dev → test → stage → prod) with artifact traceability, release re-tagging, and hotfix support. Six workflows. See the walkthrough to try it end-to-end.

What's Next?