Helm vs. JFrog Artifactory

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

It works at scale and a large number of accessible pipelines for searching, repository updates and indexing will become easier. JFrog provides end-to-end solutions for all DevOps needs. With this, Jfrog Artifactory specifically implements the management of highly available repositories, with a smooth interface and integration with all the main CI tools on the market.

Incentivized

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

Incentivized

• Stores and Manages build artifacts and packages.
• Works as container registry as well.
• Easily manages local and remote repositories along with live replication.

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

• CI/CD integration. We understood they do have a pipeline, so our organization already started with Jenkins, and my understanding is that not many orgs are using the JFrog pipeline.

Incentivized

The main problem that seems intractable is getting the checksum of the artifact. Managing container artifacts is a game changer for us during project execution, as the container artifact type exposes all base image and Docker file steps. This makes debugging or analysis easier. Jfrog Artifactory provides promotion feature and can automated from one environment repo to another environment repo before the deployment occurs.

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

Support tickets take days to respond. The most basic of questions that should be knocked out in a few hours don't get answers for days. Tickets are also closed without resolution.

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

JFrog pipelines are being used in the same ecosystem as an integrated environment, to support CI-CD devops journey. This eventually helps the existing team to use both the features of the same product in a seamless way.Similar Xray, can be used as a secure measure to protect your containers and can be used as a Static Code analysis tool which can also be integrated in a Devops CI pipeline as a Left shift security strategy.

Incentivized

• developer velocity
• uptime

Incentivized

• We now have a solid, reliable binary repository that can survive a regional outage in AWS when deployed properly
• It has allowed us to focus on building mature CICD pipelines without having to worry about an unreliable binary repository.

Incentivized