A repository contains some examples for PipeCD.
NOTE: This repository is automatically synced from the examples directory of pipe-cd/pipe repository. If you want to make a pull request, please send it to pipe-cd/pipe repository.
| Name | Description |
|---|---|
| simple | Deploy plain-yaml manifests in application directory without using pipeline. |
| helm-local-chart | Deploy a helm chart sourced from the same Git repository. |
| helm-remote-chart | Deploy a helm chart sourced from a Helm Chart Repository. |
| helm-remote-git-chart | Deploy a helm chart sourced from another Git repository. |
| kustomize-local-base | Deploy a kustomize package that just uses the local bases from the same Git repository. |
| kustomize-remote-base | Deploy a kustomize package that uses remote bases from other Git repositories. |
| canary | Deloyment pipeline with canary strategy. |
| canary-by-config-change | Deployment pipeline with canary strategy when ConfigMap was changed. |
| bluegreen | Deployment pipeline with bluegreen strategy. This also contains a manual approval stage. |
| mesh-istio-canary | Deployment pipeline with canary strategy by using Istio for traffic routing. |
| mesh-istio-bluegreen | Deployment pipeline with bluegreen strategy by using Istio for traffic routing. |
| mesh-smi-canary | Deployment pipeline with canary strategy by using SMI for traffic routing. |
| mesh-smi-bluegreen | Deployment pipeline with bluegreen strategy by using SMI for traffic routing. |
| wait-approval | Deployment pipeline that contains a manual approval stage. |
| multi-steps-canary | Deployment pipeline with multiple canary steps. |
| analysis-by-metrics | Deployment pipeline with analysis stage by metrics. |
| analysis-by-http | Deployment pipeline with analysis stage by running http requests. |
| analysis-by-log | Deployment pipeline with analysis stage by checking logs. |
| analysis-with-baseline | Deployment pipeline with analysis stage by comparing baseline and canary. |
| Name | Description |
|---|---|
| simple | Automatically applies when any changes were detected. |
| local-module | Deploy application that using local terraform modules from the same Git repository. |
| remote-module | Deploy application that using remote terraform modules from other Git repositories. |
| wait-approval | Deployment pipeline that contains a manual approval stage. |
| autorollback | Automatically rollback the changes when deployment was failed. |
| Name | Description |
|---|---|
| simple | Quick sync by rolling out the new version and switching all traffic to it. |
| canary | Deployment pipeline with canary strategy. |
| analysis | Deployment pipeline that contains an analysis stage. |
| Name | Description |
|---|---|
| simple | Quick sync by rolling out the new version and switching all traffic to it. |
| canary | Deployment pipeline with canary strategy. |
| analysis | Deployment pipeline that contains an analysis stage. |
| remote-git | Deploy the lambda code sourced from another Git repository. |
Note that the .kapetanios directory is for our CI configurations. It has nothing to do with PipeCD.