Katrina Verey
Katrina Verey
Also enhance this kind of error specifically in the namespace transformer, explaining to the user that it is probably a field spec issue. Also remove ignored field specs from that...
As described in [Open letter to Kubernetes reviewers/approvers (and contributors!)](https://groups.google.com/a/kubernetes.io/g/dev/c/6F3h0Z1QzVg/m/43tdYs_lAAAJ?utm_medium=email&utm_source=footer), the Kubernetes project is taking steps to improve the quality of our codebases for the long term. Notably: > We...
e.g. "exec" vs "execs"
- Take advantage of go1.18's [BuildInfo](https://pkg.go.dev/runtime/debug), when available, with fallback on the constants set by ldflags we use today. Should fix https://github.com/kubernetes-sigs/kustomize/issues/4617. - Add json and yaml output formats. -...
It recently came to @natasha41575 and my attention that the `configMapGenerator` has a bug where it will load values from the environment when a line in an env file has...
When you use a builtin from the transformers field, the `fieldSpecs` field defaults to empty instead of the usual defaults. That's a pretty big usability issue for Composition. Can we...
This currently doesn't work because the framework used to load builtin generators we auto-create from Go plugins treats generator vs. transformer as an exclusive choice. This is required for [Kustomize...
This is a fairly complete implementation of https://github.com/kubernetes/enhancements/issues/2299. This PR is way too big to review; I'll open separate, more granular PRs that reference this one. Besides the TODOs in...
We plan to deprecate and eventually remove Go plugins. Kustomize's own builtins, though compiled into the API module, are currently originated from Go plugins themselves. As part of the deprecation,...
## Idea It's necessarily true that each invocation of our tool only needs one of the clusters/contexts/users in the kubeconfig. If we constructed a tempfile containing only the information we...