chore: move charts to OCI registry

[Spazzy757]

Changelog

• moves helm charts to OCI registry

NOTE: Im not sure I like the -charts suffix everywhere, I think its dirty and will probably break some things, however as docker hub does not allow namespaced artifacts (i.e oci://registry-1.docker.io/vlabresearch/charts/dashboard) and without this we will clash with the images for the applications

we would need to either:

• Create a separate dockerhub org for charts as bitnami does
• Move to a more OCI compliant registry (i.e gcr)
• Figure out a hack with versions (we can maybe suffix the charts versions with -chart)

@nandanrao would love your thoughts on direction

[netlify[bot]]

✅ Deploy Preview for vlab-research canceled.

Name	Link
🔨 Latest commit	4ad7bd8fb98cd4c36d5a29933ce742d99736cf02
🔍 Latest deploy log	https://app.netlify.com/sites/vlab-research/deploys/648184f0991dc400084b7874

[netlify[bot]]

✅ Deploy Preview for virtuallab-videos canceled.

Name	Link
🔨 Latest commit	4ad7bd8fb98cd4c36d5a29933ce742d99736cf02
🔍 Latest deploy log	https://app.netlify.com/sites/virtuallab-videos/deploys/648184f0754ba70008b4cd16

[Spazzy757]

An update, I tested out if we could use the same repo for images and helm charts, looks like we can (example)

Just need confirmation this is the way you would like to go, keeping in mind if you don't add the -chart suffix to the version string it will overwrite the image that might have that version

[nandanrao]

I think you might have a better view on what the work is required for each of these routes, tbh.

My preference would maybe be to move off Dockerhub and move to another registry, like GCR. We can eventually move our containers there as well. No need to stick with dockerhub, imo.

[Spazzy757]

Went with storing the charts in Artifact Registry in Google Cloud