isopod
isopod copied to clipboard
More of helm
Nice to see you added some helm support as well. A tool like things shouldn't try to compete, but compliment.
It would be extremely useful if you where able to parse helm and then get a bunches of objects back that you can continue to work on using starlark..
This might be difficult to do using helm 2, and tiller.. but I think this is doable in helm v3.
There are many times I want to use helm as a base, but then do some additional parsing, stuff that you usually need the template to support..
Lars,
Thank you for your suggestion. Isopod offers rich features such as typed k8s objects, code reuse, unit testing configuration files, and diff against live objects in cluster, but Isopod does not replace Helm as a standard package distribution tool. We at Cruise are also motivated to support Helm in the context of Isopod. One example is to install Istio. @canthefason has been leading on this front and the helm
built-in in Isopod was his contribution. Perhaps he can comment on your proposal. We are also more than happy to accept your contribution.
A side note is that our experience at Cruise to build a multi-tenant platform on k8s has shown that Tiller is difficult to secure, and our usage of helm, if any, has been just templating but not installing/applying.
Thanks for the response! One thing that annoys me with helm is that it is difficult to do logic after helm is done rendering it's templates, and it is being applied, hence the proposal.
I'm very glad that you are not trying to compete with helm :)
Helm 3 is tiller-less and works locally, and used the normal k8s RBAC for security.. Since this proposal (if pursued) is happening, it might be fine to just support helm 3..
Under the hood, Isopod's Helm support render the manifests from the chart. So implementing Helm 3's tiller-less ability to read objects back during apply might be non-trival.
You can use kube.get
in Isopod today to read a resource back after you use the built-in Helm support to apply though.