Create Next-Build Dev and Staging EKS Environments

[olivereri]

Requirements

Accelerated Publishing needs a Helm Chart to host a Next-Build server on Platform's Elastic Kubernetes Service (EKS). Helm Charts are deployed to EKS by ArgoCD and exist in this repository: Application Manifests. First as a proof of concept and to work through errors Next-Build will be deployed to the Dev environment. CMS does not have a dev environment, so after a successful deployment to Dev, that work should be replicated for Staging.

Acceptance criteria

Preview Give feedback

1. Service requirements for Next-Build are determined. Likely a Heml files for: Service, Deployment, Configmap, DNS, and Ingress.
2. Application Manifests PR Approved and merged for Next-Build in Dev.
3. At a minimum a Hello World container is reachable in Dev.
4. Copy work in Dev to EKS Staging environment. Or auto promotion.
5. AWS Route 53 DNS record is created.

Background & implementation details

Environment Promotion may obviate the need to create Staging explicitly.

Simple CMS Dev Helm Chart:
https://github.com/department-of-veterans-affairs/vsp-infra-application-manifests/pull/190/files#diff-2d13af2fe5c0c1cc02f200fd9c18281b92994e2f030ca5a6d1b3bbf11583bc1c

[olivereri]

ALBs that send traffic to target groups that contain EKS clusters is in Terraform code:
https://github.com/department-of-veterans-affairs/devops/blob/master/terraform/applications/platform-eks-clusters/alb.tf#L73

[olivereri]

This link leads to EKS Application Onboarding. It appears that application on-boarding and promotion are the same thing. So to break down the process:

1. Fill out the on-boarding issue form in va.gov-team repository.
2. Create the application folder structure and add manifest files in the Application-manifest repository under the apps folder.
3. Update the cms.va.gov hosted zone in AWS Route 53 wigh a CNAME record pointing to the appropriate traefik hostname, i.e. preview-staging.cms.va.gov -> traefik-staging.vfs.va.gov
4. Update the appropriate Load Balancer listener rules to include *.cms.va.gov i.e. dsva-vagov-staging-tools

This a blueprint for the creation of the Production application and the other supporting tasks to make it happen.