Convert v1 to v2 setters & substituions in gcp#1398
Conversation
* 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
|
/assign @Bobgy If you look at the diff for testdata_gcp_kpt you can see that the files are mostly unchanged indicating that the substitutions match what we had before. The exception is one or two bug fixes; e.g.
|
* 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/community-distribution#1398 * kubeflow/hack/create_kptfile.py contains most of the commands used to generate the setters and substitutions.
|
/lgtm Approving first, going to take a deeper look |
| """This is a script created for the updating of the GCP Kpt packages. | ||
|
|
||
| The purpose of this is to upgrade to using setters and substitutions | ||
| """ |
There was a problem hiding this comment.
Do we just use this for upgrade?
How should users create new substitutions when working with blueprint?
There was a problem hiding this comment.
This is a onetime script. We can delete it in a subsequent PR. If we need to create additional substitutions we can do so using the kpt CLI.
When doing these types of conversions its just a good practice IMO to check in a script so we have a record in case we need to redo it.
|
/lgtm |
|
@jlewi: you cannot LGTM your own PR. DetailsIn 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bobgy, jlewi The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* 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/community-distribution#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/community-distribution#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/community-distribution#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/community-distribution#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/community-distribution#1398 * kubeflow/hack/create_kptfile.py contains most of the commands used to generate the setters and substitutions. * Disable presubmit to deploy Kubeflow.
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