<p>The introduction of Kustomize looks like an effort to fill a gap of natively managing a manifests parameterization in Kuberenetes. </p>

<p>While Helm is a mainstream player in the field.
I recognize Helm as not just a templating tool providing much more value (release version management, blue-green deploy support etc)</p>

<p>However while Kustomize is a native feature should I start preferring it assuming it's evolution in the long run?</p>

<p>UPD: while it have been put on hold as opinion based I guess it could be rephrased as What are the Best use cases  for either option. </p>

<p>It all depends on what problem you're trying to solve, but I think there's room for both.</p>

<p>There's a lot of power with helm and helm charts. Things like <a href="https://hub.helm.sh/" rel="nofollow noreferrer">https://hub.helm.sh/</a> make it very easy to distribute and package app delivery (YAML) in a centralized way.</p>

<p>Kustomize is incredibly powerful too. I have used it to inject parameters into deployments where I didn't own the original YAML or couldn't easily modify it.</p>

<p>I've seen CD pipelines where the deployment is generated from a public helm chart and then kustomize is used to inject additional parameters or requirements.</p>

<p><strong>TL;DR</strong> Use the product(s) that solve your problem and understand the value in alternatives.</p>
