Helm

“Helm and Ivy are fully featured (I always forget how much Helm has for you).”

“Helm is popular for other reasons that belie non-string wire options”

“there's a reason why shell + Helm is popular - they're stable”

“Yes, it's horrific, but it really doesn't become problematic until you are having an external system render”

“can just use a shared helm chart, customised through values.yaml”

“what is awful is using a text templating language to generate yaml with the correct level of indentation”

“Using text templating for structured documents is already quite bad, doing it with a significant whitespace language it's absolute hell.”

“I like how easy it is to maintain the configuration in a helm package”

“a complex piece of tech that requires a lot more knowledge than "just push this helm chart" to work”

“The simplest way to start probably would just be to create a custom Helm chart and define what you want in values.yaml.”

“In helm, best case you get a syntax error, worst case you end up overwriting keys and producing something syntactically but not logically correct.”

“Community charts tend to have an insane amount of "knobs" so you can basically change everything being templated.”

“the possibility to use helm to install all kinds of open source project”

“you can continue using it for a bunch of other stuff with minimal new config”

“It makes absolute sense. You can use no variables and still deploy helm chart.”

“if I test and deploy a helm chart, I know it will work everywhere in every variation”

“Helm may be ok for distributing a pre-packaged solution to other people”

“Helm is a perfectly acceptable way to quickly install K8s components”

“I would recommend anyone who wants to actually learn the fundamentals of synthesis, to start on it.”

“k8s + Helm charts can keep the rest of config in a manageable file-based state”

“Go templates are not jinja but fundamentally the same thing - they have no syntax awareness and effectively are just string formatters.”

“I like helm because it lets me encapsulate a deployment in a single package”

“Helm is not just a templating engine to provide kubernetes manifests. It’s an application deployment and distribution ecosystem.”

“I don't understand why having to "grep through the templates" is so bad.”

“the templating side saved me where it was convenient to just run a helm command with --dry-run”

“our helm charts are flat and for year only passed in the image as variable”

“once I got the hang of the template charts I don't feel like I'm running into any hurdles while using it”

“Helm is a product that serves users who like customization to the nth-degree.”

“Ive found it easier, in most cases, to run 'helm template ...' on an existing chart”

“library charts can improve the experience of creating and maintaining helm charts by a lot”

“we've debugged various Helm issues caused by the internal sprig library used”

“I don't care for helm myself but it's less bad than a lot of other approaches”

“People probably don't realize, that helm mostly is templating for the YAMLs kubernetes wants (plus a lot of other stuff that increases complexity).”

“I love using helm but I feel I got used to go templates and sub charts done right.”

“Helm requires you to write a template and you need to know (or guess) up front which values you want to be configurable.”

“Does your Kubernetes configuration need to be installed by a stranger? Use Helm.”

“A Helm chart is often a poorly documented abstraction layer which often makes it impossible to relate back the managed application's original documentation”

“our entire infrastructure is already helm so hard to switch that all out”

“the main problem with Helm charts is that every customization option needs to be implemented by the chart that way”

“They are just normal k8s templates with a couple of values parameterized, and they work great.”