[P1BIGROCKS-1502](https://jira.il2.dso.mil/browse/P1BIGROCKS-1502) ## Problem Statement As we're adding increased features and packages, it's becoming harder to convey to customers our intended best practices on how to deploy, operate, and update BB on the variety of environments our customers intend to use. We try our best to be as flexible as possible with deployment configurations, and welcoming to all cluster and infrastructure decisions, but this leads to confusion for customers looking to deploy Big bang in ways that are "recommended", or meet "best practices", or better yet, "can be ATO'd via reciprocity". ## Goals Build a set of publicly available repositories containing fully prescriptive production ready deployments of Big Bang that the team supports as "Big Bang Validated Architectures" soup to nuts. This should include: * IAC for spinning up _all_ necessary infrastructure (networking, databases, storage, cluster(s), etc...) on CSPs and on-prem * (I/C)AC for deploying and configuring all Big Bang pre-requisites * CAC for deploying Big Bang * CAC for deploying user defined applications on or besides Big Bang * Architecture Diagram (read: picture linked in `README.md`) outlining the deployable scenario The combination is _endless_, so examples owned by BB should be curated based off customer use to get the biggest bang for the buck in terms of teaching power. Examples should be fork-able for customers to use as a starting point for their Big Bang activities. ## Non-Goals * another "QuickStart" repo * `n` ^ `m` ^ `p` examples for every combination of cluster + environment + BB package combo ## Examples/Current Solutions The [dogfood](https://repo1.dso.mil/platform-one/big-bang/customers/bigbang) cluster was intended to be exactly this but morphed into our own internal dev/test infra needs. Making a public copy of this would be a suitable candidate for example repo #1 The [template](https://repo1.dso.mil/platform-one/big-bang/customers/template) repo is a partial solution, with documentation for infra + cluster up this would also be good. ## Concerns * Very easy for examples to go stale without TLC