-
Notifications
You must be signed in to change notification settings - Fork 113
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a full kustomize resource #2046
Comments
This is a really useful feature. Without being able to edit the kustomization.yaml, it restricts some fundamental principles of automation. Or maybe a way to use transformations on the kustomization.yaml file. |
This does seem like a useful feature. We should keep in mind the design principle of Kustomize (from Eschewed Features), that informed the simplistic design of the
This sentiment is also echoed here. I would advocate for a new resource type, e.g. |
Hello!
Issue details
I'm currently using https://www.pulumi.com/registry/packages/kubernetes/api-docs/kustomize/directory/. However it's quite limited because we can't override values like you normally would on the command line with
kustomize set namespace=
, etc. or your own kustomization.yaml file referring a remote resource.Instead of simply taking a directory, it would be a lot more useful if the kustomize resource could take an object which represents a kustomization.yaml itself. Then users can specify all possible options.
So something like:
So basically, just allow specifying a
kustomization.yaml
equivalent in-line. This would give full customization over a kustomize project.Affected area/feature
The text was updated successfully, but these errors were encountered: