Blueprints
A blueprint is a complete starting setup for a cloud platform, which a team can copy as is or adapt to its use case. Each blueprint picks one option for every part of the setup and links the page in this handbook that explains that part. The DevOps Handbook's blueprints cover the developer's side of the same setups.
Selection
- Simple: one cloud account and one state backend, with everything installed and deployed from CI.
- Advanced: the options a setup takes on top of Simple, each with the need that calls for it.
Start every setup from Simple, and take an advanced option only once its need is there. Each option is taken separately, so a setup takes the ones it needs and no others.
Upfront choices
Every setup makes these choices before its first resource exists, whichever blueprint it starts from, because they're fixed at creation or costly to change:
- The address plan and the network ranges taken from it: DigitalOcean and Scaleway fix a network's range at creation, and overlapping ranges can't be connected later.
- Node isolation, meaning nodes without public addresses, because DigitalOcean Kubernetes isolates nodes only in a new cluster.
- A region for each network and cluster, since neither moves to another region once it exists.
- Account layout, one account or one per environment, as resources rarely move between accounts in place.