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] bootstrapper fails to create CloudEndpoints resource #954
Comments
I exec'd into the bootstrapper and reran
The cloudendpoints resource was created. So I think it is an ordering issue. /assign @kunmingg |
OK seems |
Using ks directly might be better but not sure that will solve the problem. Maybe you just need to explicitly order the components? e.g. ks show -c metacontroller | kubectl apply |
Control oder from yaml config? |
@kunmingg Do we need to introduce new variables? Could we just create the components in the order specified in the YAML file? |
@jlewi |
* add a gauge metric for current experiments Signed-off-by: yeya24 <yb532204897@gmail.com> * fmt & fix test Signed-off-by: yeya24 <yb532204897@gmail.com>
…c0 (kubeflow#954) * image gcr.io/kubeflow-images-public/notebook-controller:vmaster-gf39279c0 * Image built from kubeflow/kubeflow@f39279c0
When I deploy on GKE I'm seeing the following error and no cloudendpoints resource is created.
I wonder if this is an issue with the ordering of resource creation.
/kind bug
/priority p1
The text was updated successfully, but these errors were encountered: