Blueprints
A blueprint is an opinionated pick from this handbook. It's a complete starting setup that a team uses as it is or adapts to its use case. Each blueprint picks one option per topic, states it in one line with its reason, and links the handbook page that explains the topic. The Cloud Handbook's blueprints pick the cloud platform that the apps run on.
- Simple: one repository per project for the app's code and deployment configuration, deployed with Helm from CI.
- GitOps: one configuration repository for the deployment configuration of every app, deployed by Flux or Argo CD.
Choosing
Start from Simple, and move to GitOps when one of these needs comes up:
- The cluster has to return to what git says after someone changes it by hand.
- One repository's history has to list every change to what runs, without code commits in between.
- The people who write the code aren't the people who may change production.
- Configuration changes, such as more replicas, have to deploy without building the app.
The move costs a second merge request for every feature that needs new configuration, and a controller that the cloud platform has to run. Repositories covers the same trade-off for the repository layout.