[CMS-Test] Kubernetes Onboarding

[olivereri]

Description of your application

Describe your application Name: CMS-Test Functionality: Test infrastructure for VA.gov Content Management System Language/Stack: PHP/Drupal Ports/Networking needed: 80/443 Other infrastructure needed e.g. Database, redis, etc: Will plug-in to existing infrastructure Anything else we need to know?:

Background/Context/Resources

Any addition information that can be provided, Slack conversations, tickets, design documents, epics, etc. https://app.zenhub.com/workspaces/vagov-cms-team-5c0e7b864b5806bc2bfc2087/issues/department-of-veterans-affairs/va.gov-cms/6285 https://github.com/department-of-veterans-affairs/va.gov-cms/issues/6357

Technical Notes

Any addition technical notes that can be provided We'd like to start by migrating the CMS-Test infrastructure to EKS. This is a solid exercise to develop and test run books for the eventual transition for Production CMS onto EKS.

Checklist of Items needed for onboarding (Responsible parties in parentheses)

• [x] Your application! (Your team) Your application should conform to the 12 factor app methodology (https://12factor.net/)
• [x] A Github Repository for your application (Operations or your team)
• [x] A Dockerfile for your application (Your team, Operations can assist if needed)
• [x] Elastic Container Registry Repository for your application (Operations, PRs are welcome: https://github.com/department-of-veterans-affairs/devops/blob/master/terraform/environments/global/ecr.tf)
• [ ] Automation to "Release" and "Tag" the application Github Repository with a semantic version number. (Your team, Operations can assist if needed)
• [ ] Automation to push the built Docker container to the ECR Repository and tag it with the semantic version number. (Your team, Operations can assist if needed) Please do not use 'latest' tags
• [x] Kubernetes Application Manifest in YAML, jsonnet, or Helm Chart (Operations and your team) YAML and jsonnet are highly preferred, Helm charts are discouraged
• [ ] Automation to update the Kubernetes Application Manifest when a new version of your application container is pushed to ECR (Operations and your team)
• [ ] AWS Service account for your team or application (Operations)
• [x] Path/s in AWS SSM Parameter Store created for your team or application (Operations)
• [x] AWS IAM Permissions applied to your team members to allow read/write access to AWS SSM Parameter Store path/s for your application/team (Operations)
• [ ] AWS IAM Permissions applied to the service account to allow read access to AWS SSM Parameter Store path/s for your application/team (Operations)
• [ ] Secrets and Parameters needed for your application stored in AWS Systems Manager Parameter Store (Your team)

[olivereri]

This is still in progress. As far as I understand it's mostly on us to complete the list items with Operations team support as necessary.

[jhouse-solvd]

Note: Removed the "operations" label for now, but it can be re-added if/when additional tasks are needed from the Platform Operations team.