Category:<\/strong> Kubernetes<\/p>\n Helm is the Kubernetes package manager. Learn how to use it to automate continuous deployments, manage configurations, and maintain versions of your applications across clusters.<\/em><\/p>\n Helm is a tool that facilitates the deployment of applications in Kubernetes through reusable templates called charts<\/strong>If Docker is the container and Kubernetes is the orchestrator, Helm is the equivalent of a package management system like apt or npm.<\/p>\n With Helm you can:<\/p>\n Helm can be easily installed from the official site or with Homebrew:<\/p>\n Use the command This will generate a structure like this:<\/p>\n The file If you already have your Kubernetes cluster running (minikube, kind, GKE, EKS, etc.), you can install your chart with:<\/p>\n You can also pass custom values from another file:<\/p>\n When you update the chart or your values, you just need to run:<\/p>\n This applies the changes without removing the current release, allowing for a continuous deployment cycle<\/strong> without downtime (as long as your containers are correctly configured with probes and rolling update strategies).<\/p>\n You can use GitHub Actions to automatically deploy when a main is pushed:<\/p>\n This workflow assumes that you have configured access to your cluster via a Helm has become the de facto standard for deploying applications on Kubernetes. Its strength lies in its template reusability, rollback capabilities, and its natural integration with CI\/CD pipelines. If you work with Kubernetes, mastering Helm is almost mandatory.<\/p>\n With just a few lines of configuration, you can automate the entire deployment cycle, from development to production.<\/p>","protected":false},"excerpt":{"rendered":" Helm is the Kubernetes package manager. Learn how to use it to automate continuous deployments, manage configurations, and maintain versions of your applications across clusters.<\/p>","protected":false},"author":1,"featured_media":602,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35],"tags":[],"class_list":["post-601","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-kubernetes"],"yoast_head":"\n
\nWhat is Helm and why should you use it?<\/h3>\n
\n
Step 1: Install Helm<\/h3>\n
brew install helm helm version<\/code><\/pre>\nStep 2: Create a Custom Chart<\/h3>\n
helm create<\/code> To generate the base structure of a chart:<\/p>\nhelm create mi-app<\/code><\/pre>\nmy-app\/ \u251c\u2500\u2500 charts\/ \u251c\u2500\u2500 templates\/ \u2502 \u251c\u2500\u2500 deployment.yaml \u2502 \u251c\u2500\u2500 service.yaml \u2502 \u2514\u2500\u2500 ingress.yaml \u251c\u2500\u2500 values.yaml \u2514\u2500\u2500 Chart.yaml<\/code><\/pre>\nvalues.yaml<\/code> contains the configuration values that you can parameterize. The rest of the files use the syntax of Go templates<\/code> to interpolate those values.<\/p>\nStep 3: Install the chart on Kubernetes<\/h3>\n
helm install my-app .\/my-app<\/code><\/pre>\nhelm install mi-app .\/mi-app -f values.prod.yaml<\/code><\/pre>\nStep 4: Update the app and make continuous deployments<\/h3>\n
helm upgrade my-app .\/my-app<\/code><\/pre>\nStep 5: Automate with GitHub Actions<\/h3>\n
name: Deploy to Kubernetes on: push: branches: - main jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions\/checkout@v4 - uses: azure\/setup-helm@v3 - run: | helm upgrade --install mi-app .\/mi-app -f values.prod.yaml\r\n<\/code><\/pre>\nkubeconfig<\/code> secure stored as a secret in the repository.<\/p>\nAdvanced Tips<\/h3>\n
\n
helm diff<\/code> to preview the changes before applying them<\/li>\nConclusion<\/h3>\n