This is the documentation for the latest development version of Cartographer. Both code and docs may be unstable and these docs are not guaranteed to be up to date or correct. See the latest version.
It is often desirable to separate build and production environments; this can be achieved with multiple clusters. Cartographer helps pave a path to production across clusters with ClusterSupplyChains and ClusterDeliveries, leveraging GitOps.
A ClusterSupplyChain can be installed into an isolated build cluster to manage the path from source code to Kubernetes configuration in a Git repository. Meanwhile, a ClusterDelivery can be installed in the production cluster, which will pick up that configuration from the Git repository to be deployed and tested. This allows for the same artifact to be promoted through multiple environments to first test/validate and finally run in production.
Example PR based flow
- Developer commits new source code
- ClusterSupplyChain in the build cluster generates Kubernetes configuration and commits it to a git repository (i.e. staging/feature-a)
- “Staging environment maintainer” opens a PR and merges staging/feature-a into staging
- ClusterDelivery in the staging cluster picks up the merged PR and deploys the Kubernetes configuration to be tested and commits it to a git repository (i.e. production/feature-a)
- “Production environment maintainer” opens a PR and merges production/feature-a into production
- ClusterDelivery in the production cluster picks up the merged PR and deploys the Kubernetes configuration.