-
Notifications
You must be signed in to change notification settings - Fork 63
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
Deploy kubeflow error: Unable to recognize "---", no matches for kind "---" #104
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Looks like your management cluster wasn't properly set up. Can you retry steps in https://github.com/kubeflow/gcp-blueprints/tree/master/management? Note, the management cluster needs to be a separate one, looks like you are installing both in the same cluster |
In the management, 5th step is creating an error.
I made some changes in the ./upstream to get The error without manual changes:
▶ kpt cfg set ./upstream name ${MGMT_NAME}
set 0 fields
Error: open upstream/Kptfile: no such file or directory
▶ make apply
# Delete the directory so any resources that have been removed
# from the manifests will be pruned
rm -rf .build
mkdir -p .build/
mkdir -p .build/cluster
kustomize build ./instance/cluster -o .build/cluster
Error: no matches for OriginalId container.cnrm.cloud.google.com_v1alpha2_ContainerCluster|~X|kf-mgmt; no matches for CurrentId container.cnrm.cloud.google.com_v1alpha2_ContainerCluster|~X|kf-mgmt; failed to find unique target for patch container.cnrm.cloud.google.com_v1alpha2_ContainerCluster|kf-mgmt
make: *** [hydrate] Error 1 Tool Versions:▶ kpt version
v0.24.0
▶ kustomize version
Version: {Version:kustomize/v3.2.1 ...
▶ gcloud version
Google Cloud SDK 299.0.0
▶ istioctl version
client version: 1.4.10-asm.15 |
Are we going to maintain two clusters? Management cluster like a parent one and another cluster for kubeflow applications that gets created using management cluster. |
Not sure if related, can you try updated instruction after #105 PR? Or probably looks like there's more changes coming in, you might want to wait a few days before all fixes are ready. @jlewi can you confirm whether current state in this repo works?
Yes, we'll have two clusters, the management cluster is meant to provide declarative GCP resource management by Kubernetes resources, it's using https://cloud.google.com/config-connector/docs/overview. You can potentially use management cluster for any other GCP resource management. |
@Bobgy @subodh101 The management cluster is broken per #102 and needs #105 as well as the related PR in kubeflow/manifests ; the pending fixes are needed. |
What?
Deploy Kubeflow is throwing effectively three errors:
More details after firing
make apply
:The text was updated successfully, but these errors were encountered: