Expanding/applying only one namespace?

[martin-hoger]

Thank you for a great tool. It works really great.

Only one thing is kind of annoying, if there is minor change that needs to be applied, the kubeapply has to expand/apply the full cluster profile and it takes relatively long as it has to go trough all the namespaces (and expand all the charts, etc...). Would be it possible to add an optional parameter that would apply/expand only a given namespace? Or possibility to exclude some namespaces/directories, or something like that?

[yolken-segment]

Glad you've found the tool useful!

We don't currently have any option for limiting the expansion step, but both the diff and apply steps support limiting to just a subset of the expanded configs via the --subpath flag. From our experience, these are the slowest ones because they actually have to hit the Kubernetes API.

For expansion, we do have some parallelization on the Helm runs (controllable via the --parallelism flag in kubeapply expand). Can you try cranking that up a bit to see if it helps? If needed, we could also add a --subpath option on expansion, but we've found that increased parallelism is usually sufficient.