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
[gcp] deploy.sh should support rerunning deploy.sh when DM configs and ks app already exist #1284
Labels
Comments
jlewi
added a commit
to jlewi/kubeflow
that referenced
this issue
Jul 31, 2018
* Check if resources like secrets already exist and if they do don't recreate them. * Prevent users from checking in their GCP secrets 1. Store them in a directory with a .gitignore file 2. Remove the secrets as soon as we are done storing them in the cluster. * Allow GCFS_INSTANCE to be set to null; e.g. export GCFS_INSTANCE= If GCFS_INSTANCE is null don't set it to some default value; instead we interpret this as the user doesn't want GCFS to be installed. * Related to kubeflow#1282 can't create GCFS for legacy network. * Related to kubeflow#1284 support rerunning deploy.sh
k8s-ci-robot
pushed a commit
that referenced
this issue
Jul 31, 2018
* Make it easier to rerun deploy.sh * Check if resources like secrets already exist and if they do don't recreate them. * Prevent users from checking in their GCP secrets 1. Store them in a directory with a .gitignore file 2. Remove the secrets as soon as we are done storing them in the cluster. * Allow GCFS_INSTANCE to be set to null; e.g. export GCFS_INSTANCE= If GCFS_INSTANCE is null don't set it to some default value; instead we interpret this as the user doesn't want GCFS to be installed. * Related to #1282 can't create GCFS for legacy network. * Related to #1284 support rerunning deploy.sh * Fix bug.
Fixed by #1308 |
saffaalvi
pushed a commit
to StatCan/kubeflow
that referenced
this issue
Feb 11, 2021
* Make it easier to rerun deploy.sh * Check if resources like secrets already exist and if they do don't recreate them. * Prevent users from checking in their GCP secrets 1. Store them in a directory with a .gitignore file 2. Remove the secrets as soon as we are done storing them in the cluster. * Allow GCFS_INSTANCE to be set to null; e.g. export GCFS_INSTANCE= If GCFS_INSTANCE is null don't set it to some default value; instead we interpret this as the user doesn't want GCFS to be installed. * Related to kubeflow#1282 can't create GCFS for legacy network. * Related to kubeflow#1284 support rerunning deploy.sh * Fix bug.
yanniszark
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Feb 15, 2021
* Add e2e test for from volume resume * Resume experiment after completion * Print controller logs * Remove test prints * Remove controller logs
surajkota
pushed a commit
to surajkota/kubeflow
that referenced
this issue
Jun 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should support the following flow
There are some minor bugs that prevent this flow from working with 0.2.2 and on master.
Some issues
* need to skip recreating the ksonnet app and modifying it if it already exists.
The text was updated successfully, but these errors were encountered: