Natasha Sarkar
Natasha Sarkar
Fixes https://github.com/GoogleContainerTools/kpt/issues/3423 cc @ChristopherFry This PR surfaces the function `Results` from the function runner library when a validation function encounters a failure (rather than returning a generic error message). As...
Proposed fix for https://github.com/GoogleContainerTools/kpt/issues/3407 Basically ignore tags that don't have a package name in front of the version, and ignore tags that throw errors. As we see in the kpt...
We recently ran into an issue where we wanted to support both set-namespace v0.4.1 and v0.3.4 as builtins in porch, but realized that with the current setup this is not...
We are using openapi data from kubernetes v1.21.2. We should consider bumping the schema version, or supporting multiple schema versions in kustomize. The openapi field syntax and the code in...
There are many open helm-related issues in kustomize: https://github.com/kubernetes-sigs/kustomize/issues?q=is%3Aissue+is%3Aopen++label%3Aarea%2Fhelm+ Many of these issues are requesting new options in the helm chart generator configuration that will become flags to `helm template`....
The docker tests in fnplugin_test.go are being skipped because docker is not available in `PATH`.
Should be merged after release containing the deprecation warnings /hold /cc @KnVerey
The following fields are slated for deprecation and will be removed in Kustomization v1: 1. `patchesJson6902` and `patchesStrategicMerge`. Only the `patches` field will be supported. 2. `bases`. To use a...
Now that the domain kustomize.io has been transferred to us, we should figure out what we want to do with all of our fragmented documentation. There's the outdated kustomize.io, the...
We should remove `patchesStrategicMerge` and `patchesJson6902` in kustomization v1. All patches can be placed in the `patches` field, so there is no reason to have three separate fields for it....