-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup the old release infrastructure #573
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Project: kubeflow-releasing It looks like #366 was the issue tracking the creation of this cluster. Although it looks like its actually a 0.6 cluster; so maybe it got recreated since #366 was merged It doesn't look like anything is running in that cluster
I'm going to delete this cluster and the associated deployments. |
* This cluster is no longer used (See kubeflow#573). These configs refer to a very old Kubeflow config; i.e. still using ksonnet. * Related to kubeflow#573
project: kubeflow-releasing
This is the old cron job for updating jupyter. We don't use this anymore (see #450) so I'm going to delete it. |
I think we can close this issue as soon as #574 is merged |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to inactivity. |
Follow on to #450
We should clean up the old release infrastructure.
e.g. we should have an old cron job for updating the jupyter web app that we can delete
The text was updated successfully, but these errors were encountered: