Helm vs. NuGet

If you need to automate the deployment of environments in Kubernetes and these environments should be easily replicable in other regions of your cloud provider or even in other cloud providers, then this is the tool for you. Just be prepared for a certain degree of complexity when creating the charts.

Incentivized

Whenever your projects need some packages which are available on NuGet it is easy to consume them with the help of tools such as Visual Studio, and MSBuild. We can add customized functionality to existing packages and can host them as a separate packages easily. Packages that depend on other packages are well managed by NuGet.

Incentivized

• Templates - The ability to create templates is really helpful and help creates a baseline for package management.
• Rollbacks - it is godsend. Period.
• Dry-run - This really is helpful when troubleshooting deployments and is great for testing out new charts as well.

Incentivized

• The built-in package explorer / manager in Visual Studio work reliably
• Integration with popular web-based repository manager is good
• Command-line options are enough even for complex use cases like publishing to private, credentials-protected repositories

Incentivized

• concurrent deployments
• templating values files

Incentivized

• Incomplete download resume in case of network disruptions
• Adding user friendly platform to add and update the packages
• Package creation option in Visual Studio

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

Not really have a choice here, especially when working with .NET Framework / .NET Core. At least the built-in GUI of NuGet helps beginners get up to speed quickly. However, advanced users would be able to be more productive with Maven / Ivy thanks to the complete text-based format. Basically, people from the Java world are spoiled by a much better dependency management system.

Incentivized

• Reduction in human effort.
• Streamline software versions and upgrades.

Incentivized

• Saves a rework by sharing the common functionalities across the projects
• Helped to optimize the given package using a central repository
• Helped to make use of existing useful packages

Incentivized