|
|
|
|
|
by fsniper
216 days ago
|
|
Most of the time discussion derails as everyone is focusing on different aspects of the experience. When you look into all the complaints one by one they are exceptionally acurate. * yaml has its quirks. - check
* text templating can’t be validated for spec comformity - check
* helm has lot’s of complexity - check
* helm has dependency problems - check
* helm charts can have too many moving parts with edge cases causing deep dive in the chart - check
and many others. However proposed solutions cut short on providing the value helm brings on.Helm is not just a templating engine to provide kubernetes manifests. It’s an application deployment and distribution ecosystem. Emphasis on the "ecosystem". * It brings dependency management,
* It provides kubernetes configuration management.
* It provides abstraction over configuration to define applications instead of configuration.
* It provides application packaging solution.
* It provides an application package manament solution.
* There is community support with huge library of packages.
* It’s relatively easy to create or understand charts with a varied experience level. A more robust and strictly typed templating system would remove at least half of this spectrum.
* The learning curve is flat.
When you put all of these in to consideration, it’s relatively easy to understand why it’s this prominant in the kubernetes ecosystem. |
|