Skip to content
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

Value for the kfilt plugin #13

Open
nyarly opened this issue Sep 16, 2020 · 0 comments
Open

Value for the kfilt plugin #13

nyarly opened this issue Sep 16, 2020 · 0 comments

Comments

@nyarly
Copy link

nyarly commented Sep 16, 2020

I'm attempting something like https://github.com/kubernetes-sigs/kustomize/blob/master/examples/multibases/multi-namespace.md

The common base is composed from the merge of several Helm charts. As a result there are many ClusterRoles, ClusterRoleBindings, and other un-namespaced resources generated. Kustomize won't merge those into the ultimate variant, because they share an id, when when the merge would be trivial (i.e. same id, but came resource). The advice from the Kustomize project is to produce a separate "whole-cluster" base. Managing this with delete patches, long term, sounds like a lot of toil.

Conversely, being able to use the kfilt plugin (which I'm looking at trying now) would let me filter out the 3 result bases from each Helm chart in a consistent way. There'll still be some work to knit them together sensibly, but filtering the resources into outputs will be much easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant