-
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
Need to replace partial setters with KptFile #89
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Locally I'm running.
|
It looks like we are running the kpt command twice
And it succeeds the first time. |
I take that back looks like its two different directories. |
I was also seeing this error message locally. I installed kpt as part of gcloud cli component, it recently upgraded to 0.30.1~. So I think we need to report it to kpt, something broke between the two versions. |
FYI, working version
Failing version, 301.0.0 which had kpt 0.30+ |
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
@Bobgy that makes sense thanks. The other possibility would potentially to add a KptFile. |
It looks like the old setter behavior is deleted so we will need to upgrade our Kptfiles. |
* Per GoogleCloudPlatform/kubeflow-distribution#89 we need to get rid of the legacy partial setters and move to using a KptFile and substitutions. * In preparation for that we want to check in a set of test data that is the result of running our kpt cfg set with a given set of values * This test data will be used to verify that the refactoring to use a KptFile doesn't change the output. * After adding the KptFile we can simply regenerate the testdata and then look at the diff to ensure there are no unexpected changes.
Running We should time it and compare it to the old version using partial setters. |
Seems like it might be an issue with my system. even version is taking a long time.
|
Looks like the problem is that kpt tries to contact the current master of the current context. My current context was pointing at a cluster that wasn't responsive. Once I switched the context it worked.
|
Filed kptdev/kpt#834 It looks like we need to update gcp-blueprints/kubeflow/instance to use the new setters otherwise it will be broken as well. |
* Get rid of enable-services.yaml as we are now using CNRM and this is in the base package. * Related to GoogleCloudPlatform#89
* Per GoogleCloudPlatform/kubeflow-distribution#89 we need to get rid of the legacy partial setters and move to using a KptFile and substitutions. * In preparation for that we want to check in a set of test data that is the result of running our kpt cfg set with a given set of values * This test data will be used to verify that the refactoring to use a KptFile doesn't change the output. * After adding the KptFile we can simply regenerate the testdata and then look at the diff to ensure there are no unexpected changes.
* Get rid of enable-services.yaml as we are now using CNRM and this is in the base package. * Related to GoogleCloudPlatform#89 * Remove cluster and iam policy patch; these are now in the base manifests. Added in kubeflow/manifests#1398 * kubeflow/hack/create_kptfile.py contains most of the commands used to generate the setters and substitutions.
* Now that we are using kptfiles; kpt will complain if we try to set a setter which doesn't exist. related to GoogleCloudPlatform/kubeflow-distribution#89
* Now that we are using kptfiles; kpt will complain if we try to set a setter which doesn't exist. related to GoogleCloudPlatform/kubeflow-distribution#89
* Get rid of enable-services.yaml as we are now using CNRM and this is in the base package. * Related to GoogleCloudPlatform#89 * Remove cluster and iam policy patch; these are now in the base manifests. Added in kubeflow/manifests#1398 * kubeflow/hack/create_kptfile.py contains most of the commands used to generate the setters and substitutions.
* Get rid of enable-services.yaml as we are now using CNRM and this is in the base package. * Related to #89 * Remove cluster and iam policy patch; these are now in the base manifests. Added in kubeflow/manifests#1398 * kubeflow/hack/create_kptfile.py contains most of the commands used to generate the setters and substitutions.
This is deploying on master: Need to get this cherry-picked onto the 1.1 branch. |
* Per GoogleCloudPlatform/kubeflow-distribution#89 we need to get rid of the legacy partial setters and move to using a KptFile and substitutions. * In preparation for that we want to check in a set of test data that is the result of running our kpt cfg set with a given set of values * This test data will be used to verify that the refactoring to use a KptFile doesn't change the output. * After adding the KptFile we can simply regenerate the testdata and then look at the diff to ensure there are no unexpected changes.
* Get rid of enable-services.yaml as we are now using CNRM and this is in the base package. * Related to GoogleCloudPlatform#89 * Remove cluster and iam policy patch; these are now in the base manifests. Added in kubeflow/manifests#1398 * kubeflow/hack/create_kptfile.py contains most of the commands used to generate the setters and substitutions.
* Get rid of enable-services.yaml as we are now using CNRM and this is in the base package. * Related to GoogleCloudPlatform#89 * Remove cluster and iam policy patch; these are now in the base manifests. Added in kubeflow/manifests#1398 * kubeflow/hack/create_kptfile.py contains most of the commands used to generate the setters and substitutions.
…ile refactoring #1398: Convert v1 to v2 setters & substituions in gcp Cherry pick of #1393 #1398 on v1.1-branch. #1393: Check in expected kpt output for Kptfile refactoring #1398: Convert v1 to v2 setters & substituions in gcp (#1401) * Check in expected kpt output for Kptfile refactoring * Per GoogleCloudPlatform/kubeflow-distribution#89 we need to get rid of the legacy partial setters and move to using a KptFile and substitutions. * In preparation for that we want to check in a set of test data that is the result of running our kpt cfg set with a given set of values * This test data will be used to verify that the refactoring to use a KptFile doesn't change the output. * After adding the KptFile we can simply regenerate the testdata and then look at the diff to ensure there are no unexpected changes. * Convert v1 to v2 setters & substituions in gcp * The latest version of kpt started choking on gcp/v2 because we were still using the old style setters and substitutions. * This PR creates a kptfile to use the new setter and substitutions. * hack/create_kptfile.py contains a script to generate lot of the setters and substitutions. * kf-vm-sa.yaml shouldn't specify the namespace; this will get set in an overlay * Move workload identity bindings for kf-admin KSA from kubeflow/instance in gcp blueprints repo into this repository. related to gcp-blueprints#89 * Fix image mirror substitution. * Create a KptFile for stacks. * Add conversion for stacks. * Add KptFile for stacks/gcp
…ck of #95 on v1.1-branch. #95: Convert setters from v1 to v2 (#97) * Convert setters from v1 to v2 * Get rid of enable-services.yaml as we are now using CNRM and this is in the base package. * Related to #89 * Remove cluster and iam policy patch; these are now in the base manifests. Added in kubeflow/manifests#1398 * kubeflow/hack/create_kptfile.py contains most of the commands used to generate the setters and substitutions. * Disable presubmit to deploy Kubeflow.
Here are the logs
I think we might have picked up an updated worker image which might have a newer version of kpt.
The text was updated successfully, but these errors were encountered: