[kozikow]

I personally would find it useful if helm would provide way of saving the template to yaml. E.g. only install helm "locally", but when deploying to prod just use plain yaml files based on config created via helm.

Why I would want it:

- Easier to do minor tweaks on top of the helm config, if variables exported by helm do not support it

- I find it elegant that all state required to restore state of the cluster are in yaml files. Helm require installation of apps for each cluster

- IIUC if app installed via helm changes between I install it on local cluster and prod cluster I may end up with different versions of the app

I know I can do "kubectl get pod/my-pod -o yaml". Firstly, I would have to figure our which variables are permanent (state variable like "nodeName" are mixed with permanent variables like "restartPolicy"). Secondly, I would also have to figure out all k8s objects that were created by helm.

[prydonius]

This is an interesting use-case, one way you might be able to achieve this is using technosophos' template plugin[1] which will allow you to skip the trip to the cluster and render templates client-side.

[1] https://github.com/technosophos/helm-template

[kozikow]

Looks like what I was looking for. Only minor nit is that I can't set --name like in helm install, but I can easily just search and replace in the yaml file.