
Helm reduces duplication and drift by turning duplicated Kubernetes YAML into a single, parameterized chart. A values file drives environment differences, so one change updates staging and production.
Follow Release Runway from a public Helm chart to a complete Helm delivery workflow, learning installation, values-driven customization, template fundamentals, linting, packaging, CI, GitOps with Argo CD, and AI-assisted review.
Verify that Helm is installed and that the active kubectl context targets the intended cluster before proceeding.
Run Helm env to reveal where Helm stores config and cache, and where it records release state in the cluster as secrets.
Connect Helm to the Bitnami chart repository by adding it, confirm it appears in the repo list, and run a repo update to refresh the local chart index.
Search your repositories with Helm SearchRepo to view chart names and their chart version and application version. Use the --versions flag to see all releases and pin a specific version.
Install a helm release by deploying the vietnamese-nginx chart as a running nginx web server in namespace team-a, using release name web, and review install notes for next steps.
Learn to inspect a Helm release by viewing its stored values and rendered manifests, using Helm get values and Helm get manifest to verify inputs against outputs.
Explore how values drive a Helm chart by configuring defaults to set replicas, image tag, and service port without touching templates, then read the default values file.
Package your dockerized app in a helm chart, set the image tag with a default to chart.yaml version via values.yaml, and create a versioned archive for sharing.
Explore how Helm 4 reads multi-document yaml values separated by three dashes and resolves them into a single final values set without errors.
Explore the dot files method in Helm for reading local config files and injecting them into config maps and secrets, with glob-based file inclusion and base64 encoding.
Learn how named templates in Helm charts encapsulate reusable logic, with examples of overriding names, generating fully qualified names, and customizing imagePullPolicy by environment.
Learn to read Helm release history with helm history, identify the deployed revision, and select a safe earlier revision for potential rollback by reviewing status, revisions, and descriptions.
Rollback a Helm release to a known good revision using the helm rollback command, restoring its configuration from history and creating a new rollback revision while confirming the restored state.
Learn how to uninstall a Helm release while ensuring Helm updates its records and removes managed objects, and choose to keep the release history using the -keephistory flag.
Run helm lint to validate your chart before install or upgrade, read findings, fix files, and repeat until the chart linted successfully with zero failed charts.
Learn to guard Helm charts by adding a values.schema.json to validate inputs, enforce required fields and types (e.g., replicaCount, image.repository), and fail early with clear errors.
Fixes a values-driven render error in helm by rendering with --debug to identify missing image.repository and image.tag in values.missingimage.yaml, then sets nginx:1.27.4 and re-renders.
Package a Helm chart by turning a chart directory into a single vergent archive with Helm package, producing a portable .tgz named from the vergent in chart.yml.
Discover why charts now live in OCI registries beside container images, removing the need for index.yaml and enabling push and pull with shared access rules.
Log in to an OCI registry with helm registry login. Push the packaged chart (.tgz) with helm push to the registry, making it a shareable artifact.
Explore how Helm 4 uses digests to guarantee exact chart content when pulling and installing from an OCI registry, pinning to the digest via the at sign to prevent drift.
Discover how to enforce secret boundaries in helm workflows by using repository secrets and secret references, piping credentials with --password-stdin, and keeping kube-config data in GitHub Actions secrets.
Helm is a tool used to package Kubernetes manifest files that are used to install a cloud-native application. Deployments, Services, Ingresses, ConfigMaps, etc. are all packed into a Helm chart. Using this Helm chart, you can deploy the app to a Kubernetes cluster the same way you use apt-get in Ubuntu, or brew on a macOS.
After completing this course, you will have a working knowledge of Helm. You'll be able not only to use ready-made Helm Charts to automate day-to-day deployments, but you'll also automate the most complex Kubernetes deployments and contribute them to the community.
I've designed this course to focus on the important parts of Helm. I did my best not to bother you with boring material that you'd seldom use in your day-to-day life as a Helm and Kubernetes engineer. Instead, I will give you the core stuff of the tool together with some tips and tricks that will let you code Helm charts like a pro in no time!
To get the most out of this course, I highly encourage you to open your laptop and do the labs that I explain in the class. There's nothing better than getting your hands dirty learning a new tool or technology. That way, by the end of this course, you'll find yourself already developing, applying, maintaining, and even sharing your very own Helm charts.
The best way to learn any tool is by using it! In this course, we'll work together to deploy ready-made Helm charts to Kubernetes using Helm. After mastering that, we'll start analyzing the Helm chart bit by bit. Along the way, you'll learn the following:
Understand why we need a package manager for Kubernetes
Deploying Helm to minikube (local Kubernetes cluster)
Understanding Helm repositories
Adding one or more Helm repositories to your system
Searching the Helm repository for your desired Chart
Using Helm to deploy ready-made Charts from popular repositories
Inspecting a Helm Chart deployment
Upgrading a Helm deployment and viewing its history
Customizing the Helm Chart to your own needs by modifying the values file
How (and when) to create your own Helm Charts
Understanding Helm Templates
Testing your Helm templates without applying them using the dry-run flag.
Revisiting Helm history by upgrading and rolling back package deployments
Using Helm functions (include, indent, nindent, toYaml, b64enc, and more)
Decision making using conditional and logical statements (IF, NOT, AND, OR)
Loop through simple and complex objects using the "range" keyword
Deep diving into Helm variables
Debugging your Helm charts
Creating your own Helm repositories and pushing Charts
Deploying even more complex Kubernetes environments using Helm Chart dependencies
Learning about popular community-based Helm projects like Chartmuseum
Extending Helm by building your own repositories
Exploring different Helm plugins to automate repetitive tasks and store charts in the cloud
Build your own Helm plugins and use custom commands and protocols
Configure Helm to create your own specific boilerplate charts using Helm starters
With a 30-day money-back guarantee, no questions asked, you have zero risk trying out this course. Go ahead and Enroll Now!