Create public validated architecture deployment for current dogfood cluster

Create a public facing repository that mimic's what dogfood currently is to be a reference deployment of BigBang.

The repository should include everything needed to run BigBang in various production environments, and should include:

• Architecture diagram for deployment on AWS (gov-cloud)
• IAC for deploying all AWS resources
  • vpc/subnets
  • k8s cluster
  • RDS for apps using databases
  • load balancers for ingress
  • any bigbang prerequisites
• "production ready" BigBang deployment values
  • multiple ingress gateways (1 for user facing apps, 1 for admin apps)
  • affinities based on node pools
  • selinux enforcing required modifications (if any)
  • certificates (can leverage letsencrypt *.bigbang.dev)
  • appropriate package sizing (most of this is already done by default)
• documentation for how to run all of the above ^, the links between the steps above do not need to be fully automated

added to epic &70 (closed)

changed milestone to %1.7.0

changed iteration to Big Bang Iterations Apr 21, 2021 - May 4, 2021

set weight to 1

added BB Documentation Standards kinddocs labels

added 1 deleted label

changed the description

changed the description

assigned to @michaelmcleroy

added statusdoing label and removed 1 deleted label

assigned to @evan.rush

changed milestone to %1.8.0

changed iteration to Big Bang Iterations May 5, 2021 - May 18, 2021

set weight to 3

I have created a terraform directory in https://repo1.dso.mil/platform-one/big-bang/customers/template/-/tree/terraform. But, I'm open to putting it https://repo1.dso.mil/platform-one/big-bang/terraform-modules/big-bang-terraform-launcher instead.

The Terraform meets most of the requirements above:

• Architecture diagram
• IAC for...
  • VPC/Subnets
  • RKE2 K8S Cluster
    • Cross-zone deployment
    • Auto-scaling
    • Security groups
  • Bastion
• Documentation

The terraform does not deploy, but does have examples for:

• MySQL RDS
• Postgres RDS

I think Big Bang handles the following by default:

• Load balancer for ingress
• Affinities
• Certificates
• Package sizing
• Production ready bigbang deployment values

I did not address the following items (yet):

• Multiple ingress gateways
• Different node pools (just a generic agent pool and server pool right now)
• SELinux (is this turned on by default in RHEL UBI 8 Iron Bank image?)

unassigned @evan.rush

changed milestone to %1.9.0