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.<p>Why I would want it:<p>- Easier to do minor tweaks on top of the helm config, if variables exported by helm do not support it<p>- 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<p>- 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<p>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.
I'm really excited to see projects like make containerized applications more available. There's a lot of awesome new projects in this space and I'm hoping that we as a community can come together and adopt a standard API for compatibility across all tools. CNR[0] is the name of the effort that is essentially extending OCI[1] to support apps (Helm, KPM, Kubernetes, Docker Compose, Docker DAB).<p>[0]: <a href="https://github.com/cn-app-registry/" rel="nofollow">https://github.com/cn-app-registry/</a><p>[1]: <a href="https://github.com/opencontainers/image-spec" rel="nofollow">https://github.com/opencontainers/image-spec</a>
I tried this out last night on my cluster (<a href="https://github.com/helm/monocular" rel="nofollow">https://github.com/helm/monocular</a>)<p>While nice looking I was hoping it provided a way to easily install and configure the variables from the ui.