[Sidekiq-UI (Staging)] - Application onboarding infrastructure request

[ewilson-adhoc]

Summary

IET is in the process of promoting our sidekiq-UI service from development to staging

Overview

• The Platform leverages container orchestration to host and deploy software applications
• Container orchestration automates the deployment, scaling, and management of containerized applications
• To learn more, see "Application Hosting and Deployment using Container Orchestration (EKS)"

---

Description of application

Sidekiq-UI is a web-based admin panel for viewing and debugging sidekiq queues.

Basic info:

Team Name:
platform-pst-iet Application Name:
Sidekiq-UI
Functionality:
Backend tool Language/Stack:
Ruby + Rack Ports/Networking needed:
Port 3002 for standard plain HTTP Other infrastructure needed:
N/A

Onboarding checklist

*The responsible parties are listed below each item in the checklist

Application repository and container

• [x] GitHub repo: https://github.com/department-of-veterans-affairs/vets-api-sidekiq-ui
• [x] Dockerfile: https://github.com/department-of-veterans-affairs/vets-api-sidekiq-ui/blob/main/app/Dockerfile

Application delivery pipeline (CI/CD)

• [ ] AWS service account for GitHub actions, ie svc-gha-team-name | Request here
  Infrastructure Team
• [ ] AWS Elastic Container Registry (ECR) repository for the app container: provide name of ECR repo here
  Infrastructure Team | PRs welcome
• [x] Automation to release and tag the app's GitHub repo with a semantic version number | Example | Docs
  Requesting team; Infrastructure Team can assist
• [x] Automation to push the app's container to ECR with a semantic version number | Example
  Note: Don't use default "latest" tag. The release system uses modified container image tags to synchronize automation. Requesting team; Infrastructure Team can assist
• [x] Kubernetes manifest in YAML, Jsonnet, or Helm Chart https://github.com/department-of-veterans-affairs/vsp-infra-application-manifests/tree/main/apps/platform-pst-iet/vets-api-sidekiq-ui/staging
• [x] Kubernetes detect and update application in vsp-infra-applications-manifests | Environments
  Requesting team; Infrastructure Team can assist
• [x] Automation to update the Kubernetes manifest when a new version of the app's container is pushed to ECR | Example
  Requesting team; Infrastructure Team can assist

Application secrets and parameters

• [x] AWS SSM Parameter Store path created for your team or app,
• [ ] AWS SSM Parameter Store parameters that the app needs to run,

[ewilson-adhoc]

Open questions:

• Should we need different service accounts and ECRs between staging and development?

• I believe the infrastructure team set the following variable for development /dsva-vagov/vets-api/dev/redis_sidekiq -- could the team create /dsva-vagov/vets-api/staging/redis_sidekiq containing the connection string for the staging redis instance

[jhouse-solvd]

Hi @ewilson-adhoc! Thanks for submitting this request. We are currently working to develop a process to allow platform crew developers (including Spike teams) to promote applications to higher environments. (See #43550).

I'm curious to know if this request can wait for us to develop that process. We don't want to block your work for too long, but I feel like this application (and your team) would be a great candidate for using that new process. We'd love to get your feedback on that process to make it work well for you.

Let me know your thoughts on timing?

[ewilson-adhoc]

@jhouse-solvd we're actually mostly done with this request :)

The only thing that we need from your team is to populate /dsva-vagov/vets-api/staging/redis_sidekiq otherwise we can close this out.

[ewilson-adhoc]

My team was able to find the variable and populate it ourselves. This can be closed out now