Pipelines
Automate the journey of code from development to production
Plural Pipelines automate Service Deployments across environments by promoting git-based changes through defined stages. With support for approval and job gates, they offer safe, customizable delivery flows.
Pipeline CRD in a Continuous Deployment Context
The Pipeline CRD defines a custom Kubernetes resource to model and automate complex, multi-stage deployment pipelines. It integrates well with continuous deployment (CD) systems by enabling declarative configuration of deployment flows, including gating, promotions, and service progression.
The top-level resource that encapsulates the deployment workflow.
- Stages represent discrete steps in your deployment pipeline.
- Edges define the dependencies and ordering between stages.
- FlowRef & ProjectRef provide contextual linkage to a broader application ecosystem.
- Bindings can control RBAC policies for reading/writing pipeline data.
PipelineStage and PipelineStageService
Each stage is a logical unit within the pipeline. These can represent environments (e.g., dev, staging, prod) or specific deployment phases.
- PipelineStageService includes:
- ServiceRef: the Deployment Service being deployed.
- Criteria: optional promotion rules that dictate when and how a service is allowed to advance.
This design fits CD by enabling conditional promotions, a critical part of automating production pushes safely.