Advanced blueprint
The Advanced blueprint lists the options a setup can take on top of the Simple blueprint, and the need behind each. Every option costs more to run than the Simple choice it replaces, so take one only when its need is there.
| Part | Option | Need |
|---|---|---|
| Accounts and state | An account per environment, with a state backend per environment or per workspace | Compliance rules that separate production from the other environments, such as DORA in EU financial services, or production credentials isolated from the rest |
| Regions | Several regions or clouds, with a services network and a VPN between clouds | Availability and scale beyond one region or cloud |
| Platform components | Flux or Argo CD | Continuous reconciliation, or the credentials that install components kept inside the cluster |
| Secrets | A secret store that the platform runs, with External Secrets Operator syncing secrets into Kubernetes Secrets | Secrets kept out of git and out of CI once deploys move to a GitOps controller |
| Application resources | A Kubernetes-native application layer, with databases and buckets declared as Kubernetes resources | Application teams that create their own databases and buckets |
| Repository | A repository of its own for the configuration that Flux or Argo CD watches | Platform components on Flux or Argo CD |