title: What's wrong with Helm? Why isn't it widely adopted and prioritized for k8s apps?
body: <p>Up to now, Helm is the only package manager that I know for K8s. It can help deploy and manage k8s application dependencies seamlessly. Why are so many K8s applications still not adopting or prioritizing it?</p>
  <p>I have used quite a few popular ones like Argo, Istio, etc. They seem to promote the default installation method to <code>$ kubectl apply -f &lt;http path to YAML config&gt;</code>. Some do support the Helm installation method but it is pushed further down below and in many cases lack docs or are outdated. A few don't even support Helm charts.</p>
  <p>How do people actually configure, deploy and manage big K8s applications with layers upon layers of dependencies like usually seen in other platforms? Do they actually manage every dependency manually? If that is the case, the technical debt will be huge as a K8s admin needs to understand every detail of the config logic for every dependency in his application.</p>