Cost monitoring backend can be installed as a standalone helm-chart repository (phase 1)

[jnywong]

Context

The current cost reporting implementation is incorporated as part of the 2i2c infrastructure repository through mounted files in the aws-ce-grafana-backend helm chart. We should separate this into its own standalone repository so that other users can independently install the cost reporting tool using helm in line with our right to replicate policy.

Definition of Done

• Set up, initialise, rename and transfer aws-ce-grafana-backend into a standalone repository, including git commit history
  • https://github.com/jnywong/jupyterhub-cost-monitoring
  • commit history migrated with https://github.com/newren/git-filter-repo
• Set up CI/CD to publish helm charts with chartpress
  • Rename from aws-ce-grafana-backend to jupyterhub-cost-monitoring
  • Setup chartpress jupyterhub-cost-monitoring#2
• Refactor the code where necessary
• Documentation to support Establish collaboration on VEDA cost reporting with Tarashish (Development Seed) #6396
  • Initial docs jupyterhub-cost-monitoring#4
  • [docs] Update architecture.md jupyterhub-cost-monitoring#5
• Manually deploy on a test hub and validate
  • [openscapes] Update terraform and helm chart configs for jupyterhub-cost-monitoring #6481

[agoose77]

We split this into two cards, 10 + 3, and marked this one as done.

[jnywong]

Thanks Angus! Thangus!