-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Deployment problem with private cluster #534
Comments
Were you following https://www.kubeflow.org/docs/guides/gke/private-clusters/? |
I got this error when I ran the bootstrap, which I knew was deprecated. |
@IronPan, is this resolved now? Can we close? |
/close |
@IronPan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
1 similar comment
@IronPan: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I created a private cluster and try to deploy the pipeline from one of the virtual machine in the same project. Here is the error:
Configure ksonnet ...
Configure ksonnet completed successfully
Initialize a ksonnet APP ...
level=info msg="Using context "default" from kubeconfig file "/root/.kube/config""
level=error msg="unable to find SHA1 for repo: Get https://api.github.com/repos/ksonnet/parts/commits/master: dial tcp
192.30.253.117:443: i/o timeout"
Initialized ksonnet APP completed successfully
ln: failed to create symbolic link 'ml-pipeline-app/vendor/pipeline': No such file or directory
/pipeline/deploy.sh: line 142: ml-pipeline-app/tmp.yaml: No such file or directory
mv: cannot stat 'ml-pipeline-app/tmp.yaml': No such file or directory
namespace kubeflow exist
/pipeline/deploy.sh: line 155: cd: ml-pipeline-app: No such file or directory
/pipeline/deploy.sh: line 156: cd: ml-pipeline-app: No such file or directory
/pipeline/deploy.sh: line 157: cd: ml-pipeline-app: No such file or directory
/pipeline/deploy.sh: line 158: cd: ml-pipeline-app: No such file or directory
/pipeline/deploy.sh: line 159: cd: ml-pipeline-app: No such file or directory
/pipeline/deploy.sh: line 160: cd: ml-pipeline-app: No such file or directory
/pipeline/deploy.sh: line 161: cd: ml-pipeline-app: No such file or directory
/pipeline/deploy.sh: line 162: cd: ml-pipeline-app: No such file or directory
/pipeline/deploy.sh: line 163: cd: ml-pipeline-app: No such file or directory
Operation "operations/acf.9558106a-a70c-47da-80b8-8be4a32e0692" finished successfully.
ERROR: (gcloud.iam.service-accounts.keys.create) RESOURCE_EXHAUSTED: Maximum number of keys on account reached.
retryDelay: 86401s
The text was updated successfully, but these errors were encountered: