azimuth-cloud / azimuth-charts Goto Github PK

This is a series of tasks:

• Make a kustomization referring to the kubeflow manifests at the latest tag, which produces the required manifests and commit to this repo.
• Generate a Helm Chart using the above kustomization. Use this for inspiration and turn it into a script that lives in this repo. Run the script and commit the script and output to this repo. The CI will handle adding the Helm chart to the repository.
• Make an azimuth-ops branch that has this chart as an app template, then deploy through Azimuth and access via port-forward and the example user.
• Add Zenith reservation and client CRDs to proxy the istio ingress gateway with no authentication (kubeflow's default auth applies, but it gets a Zenith domain).
• Make a kustomization to enable Dex to understand the X-Remote-User header sent by Zenith and regenerate charts.

we should bump to 3.0.2 upstream chart - https://hub.jupyter.org/helm-chart/

https://discourse.jupyter.org/t/jupyterhub-deployment-on-k8s-1-27/19646/6

Once #5 is merged, the charts in this repo will use StackHPC's ghcr mirror for container images. This means that bumping the version of an upstream chart (e.g. jupyterhub) may lead to a situation where newer container images which are required by the chart are not yet synced into ghcr. We should be able automate/catch this issue by running helm template on the chart and then parsing the output for container images which can then be added to the skopeo manifests. It may even be possible to extend the existing skopeo workflow to completely automate the generation of skopeo manifests by parsing the output of helm template.