[_def]

tangent: how do people in general manage their k8s yaml? Do you keep manifests around, or stuff them away in helm charts? Something completely different? I especially wonder about ways to manage deduplication

[vbezhenar]

For deployment descriptors that I need to write, I'm using kustomize templating everywhere. Works good enough for me, so never felt the need to reach helm or anything else.

I also use helm for some software, but I never edit it, just configure using values.

Honestly it all seems like craziness and the day kustomize will not be enough for me, I'll just write small JavaScript program generating JSONs. Don't need to make it harder than that...

[seer]

We use terraform to manage both raw manifests as well as helm charts. It works reasonably well for either, just need to configure to ignore some annotations from time to time.

This allows one to easily stitch together both k8s as with all your other infra.

[NewJazz]

I've done a lot of ways:

* k8s yaml in the repo, kubectl

* kustomize

* tanka and jsonnet

* pulumi

So far jsonnet is the only method that I've used successfully for a long time. I'm working on some new stuff with pulumi, though.