Helm... some time invested at the beginning with configuration and learning, but a lot of saved time later!
Overall Satisfaction with Helm
We use Helm in some Kubernetes-based environments. Mainly as a solution for deploying existing solutions that come to us based on Helm. I can give as an example the NoSQL database stacks we use that are fully implemented in our containerized environments via Helm charts. This model greatly facilitates updates and customizations that eventually become necessary.
Pros
- Infrastructure duplication
- Customization of environments
- Applying of security updates
Cons
- Customization of Helm charts is not a trivial thing
- Too much dependent on community components.
- Don't manage as should, sensitive values (depending on third apps)
- Scalability
- Automation
- Keeping infrastructure as a code.
- Speed on deployments
- Source code as a documentation of our environment
- Reliability since Helm is a consolidated tool with a vast of resources
- Helm
We have a natural trending to use what is a reference in its space and Helm has being leader in its area for a long time. Since it has all features we need didn't make sense to us to invest time on researching and testing other alternatives, so Helm was our first and only tool in regards of automating deployments on Kubernetes.
Do you think Helm delivers good value for the price?
Yes
Are you happy with Helm's feature set?
Yes
Did Helm live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Helm go as expected?
Yes
Would you buy Helm again?
Yes
Comments
Please log in to join the conversation