needs update about hitchhikers-guide HOT 5 OPEN

The only bit where we use s2i-sre-notebook and s2i-custom-<>-notebook reference is in the image list.
https://github.com/thoth-station/helm-charts/blob/c33ec645e1f3b9ceac09db3c2bc945b042659a24/charts/meteor-pipelines/templates/meteor_generate-jupyterhub.yaml#L37

As we use the latest tag reference, the new release of those images is automatically included in new runs of meteor in Smaug cluster.

from hitchhikers-guide.

idk how the get the new releases into smaug cluster, so that meteor pipelines will use them?! @tumido

from hitchhikers-guide.

I think we did it via ArgoCD, but since the repo moved and repo structure changed we didn't update the apps:

The UI:
https://github.com/operate-first/apps/blob/master/argocd/overlays/moc-infra/applications/envs/moc/smaug/operate-first/meteor-shower.yaml

The operator:

• https://github.com/operate-first/apps/blob/master/argocd/overlays/moc-infra/applications/envs/moc/smaug/operate-first/meteor-operator-pushgateway.yaml
• https://github.com/operate-first/apps/blob/master/argocd/overlays/moc-infra/applications/envs/moc/smaug/operate-first/meteor-operator-pipelines.yaml

We may have initially deployed the pipelines through thoth-station/helm-charts, but I've lost track of it:
https://console-openshift-console.apps.smaug.na.operate-first.cloud/helm-releases/ns/aicoe-meteor

I'd suggest you adjust the ArgoCD apps to the new repo structure and take it from there... 🤷

from hitchhikers-guide.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from hitchhikers-guide.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

from hitchhikers-guide.