You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KUBEFLOW_REPO must be an absoulute path to specify a preexisting local kubeflow package. Should this path be absolute as the default is set to kubeflow_repo (which then gets augmented to its abolutute path contrary to the externally set env variable? See: https://github.com/kubeflow/kubeflow/blob/master/scripts/gke/deploy.sh#L18
If GCFS_INSTANCE is not set but the GCFS instance already exists then the waithere will terminate the script as there is no PID existing. Checking upfront if the instance exist (as mentioned in @jlewi 's comment here should fix that.
Also, how much time is saved by creating the GCFS instance directly (and in parallel/async) as opposed to via deployment manager?
There are multiple small issues with deploying kubeflow to GKE via [deploy.sh] on HEAD.(https://github.com/kubeflow/kubeflow/blob/master/scripts/gke/deploy.sh)
KUBEFLOW_REPO
must be an absoulute path to specify a preexisting local kubeflow package. Should this path be absolute as the default is set tokubeflow_repo
(which then gets augmented to its abolutute path contrary to the externally set env variable? See:https://github.com/kubeflow/kubeflow/blob/master/scripts/gke/deploy.sh#L18
If
GCFS_INSTANCE
is not set but the GCFS instance already exists then thewait
here will terminate the script as there is no PID existing. Checking upfront if the instance exist (as mentioned in @jlewi 's comment here should fix that.Also, how much time is saved by creating the GCFS instance directly (and in parallel/async) as opposed to via deployment manager?
Creating the local variable here: https://github.com/kubeflow/kubeflow/blob/master/scripts/gke/deploy.sh#L149
raises an error as it's not called in a function.
The text was updated successfully, but these errors were encountered: