Helm vs. Spinnaker

Deployment of helm charts is really fundamental to any software packages to our Kubernetes/docker containers, and without Helm, I cannot imagine how else to manage software components upgrades. When it works, it works great, when it doesn't - the world has not come to an end, there is rollback, and it's great, but troubleshooting does take time. And there is a learning curve. But it be worth it.

Incentivized

Spinnaker is a strong solution for Continuous Deployment being able to manage enormous environments in an easy way. Even Spinnaker being able to manage environments based on cloud instances (ec2 for example) I believe it is more suitable for containerized environments. Mainly in Kubernetes where it excels as a reliable and safe tool

Incentivized

• Infrastructure duplication
• Customization of environments
• Applying of security updates

Incentivized

• The immutable way of deployment is one of its greatest advantages.
• We have a strict policy to restock our instances with new images very frequently and this can be done very seamlessly via Spinnaker
• Rollback/ resize of clusters is one of the coolest features of Spinnaker.

Incentivized

• It would be great if there is verbose mode in Helm errors. Not sure if it's a thing. But more detail in the errors do helps, at times.

Incentivized

• Integration with external authentication mechanism is not that simple.
• Its configuration is made by a external tool (halyard). Would be better if we could configure it by using its own frontend.
• Its user interface is some times a bit confusing.

Incentivized

We didn't really need support, but the open-source community seemed responsive and informative when it came to issues. Many cloud native consultancy companies (including ourselves) offer support for Helm.

Incentivized

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

Incentivized

• Pipeline Expressiveness • Self-Service/Override • Visibility of Client Teams • Operability of Client Teams - • High-Quality Integrations (AWS, IHP, Google) • Extensibility – (Ability to add code) • The maturity of Deployment Process • Speed/Ease of Onboarding

Incentivized

• developer velocity
• uptime

Incentivized

• It's open source!
• RPM based deployments can be scripted at Maven file itself , so very easy!
• RPM based deployments bundles all code and configs together, so awesome!

Incentivized