Watch the full webinar for Highway to Helm: Operationalizing Kubernetes App Delivery here.

We're all fans of AC/DC, but as it turns out, a lot of Kubernetes developers are fans of Helm charts, as well. In fact, at Replicated, where we get to work with some of the most sophisticated software companies around, we see customers leveraging Helm charts more and more. As a result, we've picked up a thing or two about Helm chart best practices and decided it was time to share the knowledge. David Hallinan, Director of Content, and Fernando Cremer, Solutions Engineering Manager at Replicated, sat down to give us the scoop on all things Helm charts in a webinar aptly titled, "Highway to Helm: Operationalizing Kubernetes App Delivery."

Helm Classic came to be in 2015 and was unveiled at the inaugural KubeCon that November. In January 2016, Helm Classic merged with Google's Deployment Manager for Kubernetes. The repository now stands as the main Helm project. After joining the Cloud Native Computing Foundation (CNCF) as an incubation project in 2018, Helm Native graduated from the CNCF in April 2020. Since then, it has counted large enterprises such as AT&T, Conde Nast, JD.com, Microsoft, and VMWare as avid users.

In case you're wondering what led to the popular, open-source package manager's ascent and high adoption rate, "Highway to Helm" covers it all. We unearth details from developer yore about the pre-Helm days, where they had to manually define manifests for anything they wanted to run (such as apps, databases, and load balancers). We then discuss how developers collectively breathed a sigh of relief when Helm's better-templated approach emerged.

If you're resolute on setting up your engineering teams for success, you've come to the right place. You'll hear details on how Helm helps to standardize deployment patterns for Kubernetes apps. You'll also listen in as we decode the onerous snowflake instance. Wait, what's a snowflake instance, you say? Fret not. We've got you covered!

Helm does fantastic things, and developers use Helm charts in very creative ways. But with all that control and possibility in developers' hands, things can quickly go wrong. A perfect example is when an independent software vendor (ISV) delivers Helm charts to its customers, who fork the charts and start doing things differently, such as adding new unique values. These changes lead to increased support burden and end-customer time spent reconciling updates. We've got your back with the best plan of attack to put up guardrails, avoid pitfalls, preserve code fidelity, and go full scale ahead with Helm.

Before wrapping with a handy attendee Q&A, Replicated's resident Kubernetes expert Fernando walks you through a demo. You'll discover how Replicated works with Helm, plus the best ways to operationalize the delivery of Kubernetes apps. His demo includes details on:

• Deployment options
• Tooling to create packages (for those with less Kubernetes expertise)
• Package creation
• Promotion for channel releases
• Creation of manifests using the kURL installer

"Highway to Helm" contains tons of great information and valuable polls with exciting results on Helm usage in production. Want to know how to avoid a snowflake instance in Helm? Have you ever heard of the blue-green scenario? It's all in the on-demand webinar, which you can watch by clicking here.

About Replicated

Replicated is a platform for delivering and managing enterprise software to any customer environment, whether a VPC, customer-controlled data center, or locked-down air gapped server. Replicated has enabled some of the biggest names in tech, such as HashiCorp, Puppet, and SmartBear, to ship and manage Kubernetes clusters to customers. To discover why 60% of Fortune 100 companies are consuming software delivered and maintained by Replicated, click here to schedule a demo.