Helm Masterclass: 50 Practical Demos for Kubernetes DevOps

Sign up for Docker hub, install Docker desktop, enable the Kubernetes cluster in Docker, deploy a simple Kubernetes service and deployment, test the cluster, and install the helm cli.

Install Docker Desktop on macOS, sign up for Docker Hub, and enable a single-node Kubernetes cluster under the personal plan.

Install Docker Desktop on Windows, configure kubectl in the Docker resources bin path, verify kubectl version, and prepare to enable the Kubernetes cluster.

Set up kubectl on your Docker Desktop Kubernetes cluster by validating installation, configuring kubeconfig, and switching context to Docker Desktop, then verify nodes and contexts for seamless helm-focused deployment.

Verify docker desktop kubernetes cluster functionality by applying the cube manifest to deploy a two-replica sample app. Access localhost:31300 through the node port to view the demo, then undeploy.

Install the helm cli across macOS, Windows, and Linux using package managers or tarball, then verify with helm version and explore helm env to view environmental variables and plugin paths.

Install helm cli on Windows by downloading the zip release from GitHub, extracting to a helm folder, updating the path, and verifying with helm version.

Learn to install helm charts on a Kubernetes cluster, add the Bitnami repo, and manage releases using helm install and helm uninstall, plus kubectl get pods, services, and deployments.

Explore helm repo list, add, and search commands using Bitnami charts and Artifact Hub to locate Nginx, MySQL, and WildFly charts and prepare installations.

Install and verify a helm release by updating repos, installing Nginx from a Bitnami chart with a release name, and inspect release status in yaml or json.

Upgrade Helm charts using the set option, advancing from 2.0.0 to 4.0.0 with image tag changes, verify each version in the browser, and explore helm history and helm status commands.

Review and add a custom helm repo from Stack Simplify, search for my chart one, and install it with helm to create the my app one release.

Upgrade the release my app one from 1.0.0 to 2.0.0 using helm upgrade, verify pods, deployments, and services, and access the v2 app at localhost:31231.

Explore how helm install uses the chart app version as a default image tag, and how helm upgrade with image tag updates to 2.0.0, 3.0.0, and 4.0.0.

Execute Helm upgrade with the set option to scale replicas and verify changes with kubectl get pods, then explore Helm history and Helm status to review revisions, deployments, and resources.

Uninstall the my app one release and verify no helm releases remain by running helm list.

Discover how to upgrade with chart versions, search repo using helm search repo --versions and --version, install with a release name, and rollback from v4 to v2.

Search helm repo for my chart two, list all chart versions with --versions, and review chart versus app versions (010–040) via GitHub and artifact hub.

Install and upgrade Helm releases by specifying chart versions, observe status and resources, access the app, and upgrade to specific versions (0.1.0, 2.0.0) and the latest 4.0.0.

Learn to rollback a helm release to a prior or specific revision, examine revision history, and verify status with helm status and kubectl describe pod.

Learn how to uninstall a helm release with the --keep-history flag, retain release history for rollback to prior revisions, and verify status with helm history and status commands.

Learn how uninstalling a Helm release without the keep history flag affects Helm list, Helm history, and rollback, and why keeping history aids testing and auditing.

Use helm install with the --generate-name flag to auto create a unique release name, avoiding duplicates in devops pipelines. Demo deploys a chart with deployment and nodeport service at localhost:31231.

Learn how the Helm install --atomic flag automatically deletes a failed release and waits for all Kubernetes resources to be ready within the timeout, avoiding conflicts from failed node ports.

Demonstrate installing a helm chart with the --atomic flag to automatically rollback or uninstall a failed release, as shown when QA 101 fails and is removed.

Learn to deploy helm releases into a dev namespace using --namespace and --create-namespace in Kubernetes. Understand listing that namespace with helm list, and that uninstall does not remove the namespace.

Learn to create a dev namespace, install a helm release, upgrade to a new chart version, and uninstall resources while deleting the namespace as needed.

Learn to override helm values with -f or --values and --set, use dry-run and debug, and extract release data with helm get values, manifest, nodes, hooks, and all.

Override values with helm --set and inspect dry-run outputs to preview Kubernetes templates for deployment and service. Use --debug to see computed values and the node port changes.

Override helm release values using -f or --values with my values.yaml to set two replicas and port 31250, and verify the upgrade with a dry run.

Learn how to use helm get values to fetch release configurations, and how helm get manifest and helm get all reveal generated manifests and notes.

Understand the values hierarchy in helm by overriding parent and subchart values.yaml with -f and --set. The lecture demonstrates dry-run and actual uninstall using helm list and helm uninstall.

Delete a default key by passing null in values.yaml, overriding defaults, and let Helm dynamically allocate a nodeport; learn to use dry-run and debug for safe deployments.