{"id":584,"date":"2024-04-19T07:48:16","date_gmt":"2024-04-19T07:48:16","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=584"},"modified":"2024-04-19T07:48:16","modified_gmt":"2024-04-19T07:48:16","slug":"how-to-deploy-helm-charts-using-argo-cd","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=584","title":{"rendered":"How to Deploy Helm Charts Using Argo CD"},"content":{"rendered":"

In this blog, we are going to learn how to deploy Helm Charts using Argo CD.<\/p>\n

Helm charts are templates that can be used again and again just by changing the values on the values.yaml<\/strong> file according to your requirements.<\/p>\n

In this guide, we will look at how helm charts can be used with ArgoCD to deploy single and multiple environments.<\/p>\n

Setup Workflow<\/h2>\n

A simple diagrammatic overview of this setup is given below<\/p>\n

\"Deploy
Click to View in HD<\/span><\/figcaption><\/figure>\n

Setup Prerequisites<\/h2>\n

The following are the prerequisites for this setup.<\/p>\n

    \n
  1. Kubernetes Cluster<\/a><\/li>\n
  2. Kubectl<\/li>\n
  3. Argo CD<\/a> installed in your cluster<\/li>\n
  4. Helm installed<\/a> in your system<\/li>\n<\/ol>\n

    Helm Chart Repository<\/h2>\n

    You can use the below repository as an example or you can your own helm repository.<\/p>\n

    Clone the repository to your workstation.<\/p>\n

    git clone https:\/\/github.com\/kubernetes-learning-projects\/helm-chart.git<\/code><\/pre>\n
    For this demo, we will use the java-app<\/strong> helm chart that is part of this repository.<\/p>\n
    Once the repository is cloned, cd in to the java-app<\/strong> folder using the following command<\/p>\n
    cd java-app<\/code><\/pre>\n
    You can see the following directory structure.<\/p>\n
    .\n\u251c\u2500\u2500 Chart.yaml\n\u251c\u2500\u2500 templates\n\u2502   \u251c\u2500\u2500 configmap.yaml\n\u2502   \u251c\u2500\u2500 deployment.yaml\n\u2502   \u2514\u2500\u2500 service.yaml\n\u2514\u2500\u2500 values.yaml<\/code><\/pre>\n
    The Chart.yam<\/code>l<\/strong> file contains the name, description, type, and version of the helm chart.<\/p>\n
    Inside the templates<\/code><\/strong> folder that contains the YAMl template of the application which gets values from the values.yaml<\/code><\/strong> file.<\/p>\n
    The values.yaml<\/code><\/strong> file contains values that will be substituted into the YAML templates inside the templates<\/strong> folder during deployment.<\/p>\n
    To get a detailed understanding of Helm Charts, visit the creating helm chart<\/a> detailed blog.<\/p>\n
    Deploy Helm Charts using Argo CD<\/h2>\n
    For the purpose of demonstration, we will assume, we have two environments named dev and prod.<\/strong><\/p>\n
    First, we will be deploying the helm chart in a single environment<\/strong> dev and then will be deploying the helm chart on two environments dev and prod<\/strong>.<\/p>\n
    Lets get started with the setup.<\/p>\n
    Deploy Helm Chart in a Single Environment:<\/h3>\n
    First, let’s see how to deploy a helm chart in a single environment using Argo CD.<\/p>\n
    This is a basic helm deployment with just a single values.yaml<\/code><\/strong> file.<\/p>\n
    Now, login to your Argo CD UI and press the add NEW APP<\/strong> button to configure the GitHub repository which has the helm chart.<\/p>\n
    \"press<\/figure>\n
    A new page will appear to give the configuration for your application, specify the Application <\/strong>Name, give the Project Name<\/strong>, and select the SYNC POLICY <\/strong>as shown below<\/p>\n
    \"\"<\/figure>\n
    In the above image, you can see the AUTO-CREATE NAMESPACE<\/strong> sync option is selected, so you don’t have to create a namespace manually Argo CD will create the namespace if not present.<\/p>\n
    Then, add the URL of your Git repository, and the path of the helm chart. In our case its java-app<\/strong> folder.<\/p>\n
    \"Selecting<\/figure>\n
    Then, select you’re destination cluster URL and the namespace where you want to deploy the helm chart.<\/p>\n
    \"\"<\/figure>\n
    As you can see I am selecting the default cluster which is the cluster my Argo CD is running on, if you have multiple clusters configured to Argo CD select the cluster URL where you want to deploy.<\/p>\n
    And we are deploying the application on the pet-clinic-app<\/strong> namespace, the namespace you specify will be created by Argo CD is not present because of the AUTO-CREATE NAMESPACE<\/strong> sync option selected.<\/p>\n
    \"Helm<\/figure>\n
    Below that, you can see Argo CD automatically detects the files in the Github repository as helm chart and will show you the values of the values.yaml<\/strong> file as shown below<\/p>\n
    \"Helm<\/figure>\n
    You can alter the values as per your requirements, and if the chart type is not detected automatically you can select the type as shown below<\/p>\n
    \"Helm<\/figure>\n
    Then, press the Create button at the top of the configuration, then it will deploy the YAML file and create a dashboard for it as shown below<\/p>\n
    \"Helm<\/figure>\n
    As you can see ArgoCD gives every information about the deployment on the dashboard.<\/p>\n
    Deploy Helm Chart on Multiple Environment<\/h3>\n
    To do this you have to create two value files as shown below<\/p>\n
    .\n\u251c\u2500\u2500 Chart.yaml\n\u251c\u2500\u2500 templates\n\u2502   \u251c\u2500\u2500 configmap.yaml\n\u2502   \u251c\u2500\u2500 deployment.yaml\n\u2502   \u2514\u2500\u2500 service.yaml\n\u251c\u2500\u2500 values-dev.yaml\n\u2514\u2500\u2500 values-prod.yaml<\/code><\/pre>\n
    One of the differences in both methods is, that while using a single values file the values will be shown on the UI and you can alter the values from the UI.<\/p>\n
    But with multiple values files, you cannot change the values from the UI, you can only select the values file you want to use as shown below.<\/p>\n
    For this method, you have to create NEW APP<\/strong> two times, do the same steps you did in the above single environment method until the helm values.yaml<\/strong> file selecting step.<\/p>\n
    \"\"<\/figure>\n
    Do the same steps again and select the next values file<\/p>\n
    \"Helm<\/figure>\n
    If you want to change the values, you have to modify the values file from your local workspace and push it to Git.<\/p>\n
    After deploying the helm chart on two environments you can see your application on the dashboard as shown below.<\/p>\n
    \"Helm<\/figure>\n
    I have deployed both applications on the same cluster, if you want to deploy both applications on different clusters you can change the cluster URL in the destination section.<\/p>\n
    You may ask, why we have to create multiple value files for multiple environments and why can’t we use a single value file and change the values while deploying the helm.<\/p>\n
    We can do that also, but it is only suitable for basic applications with a minimum number of values, it is not possible for large organizations that have an application with different deployment requirements per environment.<\/p>\n
    They can’t change the values every time they deploy, so they keep fixed values for each environment and change the values on each value file if needed.<\/p>\n
    Conclusion<\/h2>\n
    In summary, you learn about integrating Helm on Argo CD and also about deploying applications on both single and multiple environments with values files.<\/p>\n
    I hope you find this blog useful and easy to understand about Argo CD helm integration.<\/p>\n
    \n
    Ngu\u1ed3n:<\/strong> How to Deploy Helm Charts Using Argo CD \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
    Source: https:\/\/devopscube.com\/how-to-deploy-helm-charts-using-argo-cd\/<\/p>\n","protected":false},"author":1,"featured_media":585,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-584","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/584","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=584"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/584\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/585"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=584"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=584"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=584"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}