Helm Masterclass

Engage with course feedback to improve the Helm masterclass, as your input helps identify student struggles and strengthens learning, while collaborative help from peers and the instructor adds value.

Explore the differences between Helm 2 and 3, including Tiller removal, a local Helm client, chart repositories, and automated deployment pipelines.

Set up minikube using the provided links and install VirtualBox on Mac, Linux, or Windows. Run the single-line install commands and verify the environment with the shown command before deployment.

Set up Visual Studio Code as your primary editor, install essential plugins for YAML support and error checking, and organize a dedicated course workspace folder.

Jump into the home demo, open the integrated terminal, create your first helm chart, name it, and then return to the explorer to see the my first chart folder.

Explore templating and value interpolation in deployment files, building a simple demo with a deployment, a service, and a service account while mastering fundamentals.

Deploy a helm chart locally in a single command by creating a chart from the current folder and installing it with helm install, enabling quick local testing and visibility.

Deploy a helm chart by creating a deployment and service, view deployments and services, copy the service ip, and verify in a browser, then leverage values files for customization.

Learn how to tear down a Helm chart deployment with a single command, remove all resources, and verify with helm list, harnessing templating to manage complex setups.

Explore challenge 1 in the Helm Masterclass as you create a chart, template deployment and service, then deploy to verify node port 31234 serves the Apache page.

Walk through completing a Helm challenge by creating a chart, configuring deployment and service, and templating image and version. Verify the deployment with a VIP and uninstall.

Open this section to learn two practical, industry-tested troubleshooting techniques for Helm, designed to save you time by fixing common indentation or missing element issues early.

Master practical helm troubleshooting by spotting templating issues such as missing curly braces with command line feedback and helm lint checks, and catch problems before packaging and deployment.

Use a Swiss army knife troubleshooting trick for helm, substituting values with the helm template to diagnose missing pieces and simulate deployment.

Master helm troubleshooting by using helm template to generate yaml, simulate deployments with kubectl create, and resolve missing deployment names through values yaml.

Master advanced helm concepts and templating logic in the beyond basic section, building on earlier lessons to deepen your ability to use helm effectively.

Copy the values file as production.yaml, deploy with helm install using -f production.yaml, check the pods with get pods, and uninstall with helm uninstall.

In the helm masterclass, prefer include over template to access helm functions, indent content by four spaces, and specify what to include to render properly formatted output with labels.

In this Helm Masterclass lecture, learn how to use if, else, and else if statements to handle multiple proxies and default options, with common comparison operators.

Develop helm conditional logic for deployments and services, using if statements for no port, a port for load balancer, and cluster IP, with templating of an engine x container section.

Complete challenge 2 by using helm templating, configuring if statements and ports, and ensuring correct indentation to generate and deploy a templated Ingenix context.

Explore how ChartMuseum stores Helm charts and acts as a central repository for deployment anywhere. Learn to set up ChartMuseum and use multiple storage platforms.

learn to install the chart museum from the terminal, copy commands, pull the chart, and edit the yaml file.

Set up a helm repository, add the stable repo, and run helm repo update to refresh repository data so you can pull down Chot Museum using the integrated terminal.

Learn to pull a chart from a chart museum, extract the tar file, and deploy into a Kubernetes cluster after updating the necessary values.

Edit values to disable the Decebal API and enable API-based chart pushing, then adjust the service port to 30001 within the 30000-32767 range, and deploy via the integrated terminal.

Deploy the Chope Museum, verify it's working, and access the Mineka IP in a browser using the node's import number, thirty thousand and one, to see Welcome to Chop Mesial.

Verify the museum repository is installed and add it as a helm repo. List repos with helm repo list to confirm, then package a chart and push to chart museum.

Create and package your first helm chart, inspect the folder, update the version in chart.yaml, and push the chart to chart museum.

Push charts to chart museum using the data payload and endpoint, then verify the chart is saved; enable API access in the values file if you see not found.

Verify a chart is pushed to chart museum and install it from chart museum using Helm, name the release, run Helm list, and uninstall it when finished.

List helm repositories, remove the repository by name with helm repo remove <name>, and verify the deletion.