{"id":271,"date":"2026-03-26T04:58:00","date_gmt":"2026-03-26T04:58:00","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=271"},"modified":"2026-03-26T04:58:00","modified_gmt":"2026-03-26T04:58:00","slug":"setup-argo-cd-using-helm","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=271","title":{"rendered":"How to Deploy Argo CD on Kubernetes: A Beginner’s Guide"},"content":{"rendered":"

In this blog, we will look at Argo CD installation on Kubernetes using step-by-step instructions.<\/p>\n

After the installation, we will look at deploying sample applications the GitOps way<\/strong>. We will use a git repository to deploy the application using Argo CD.<\/p>\n

We will also look at configuring GitHub webhooks to enable the sync process as soon as there is a change in the configured git repository.<\/p>\n

Before going into the setup, make sure you have a clear understanding of the Argo CD architecture<\/a>.<\/p>\n

What is Argo CD?<\/h2>\n

Argo CD<\/a> is a declarative, GitOps CD tool for Kubernetes, which helps you to manage applications using the Kubernetes<\/a> deployment YAML file stored in the Git repository.<\/p>\n

Argo CD uses the GitOps principle, which means Argo CD continuously monitors the repository, detects changes, and deploys them.<\/p>\n

Argo CD uses a pull-based deployment, which means whenever a change is made to the deployment<\/a> YAML file in the GitHub repository, Argo CD detects, pulls, and automatically deploys the latest changes.<\/p>\n

Given below is a simple workflow of Argo CD components.<\/p>\n

\"argocd<\/figure>\n

Below is the list of each Argo CD component.<\/p>\n

    \n
  1. argocd application controller (Statefulset):<\/strong> A core component of Argo CD that is responsible for managing and synchronizing applications (reconciliation) deployed in a Kubernetes cluster with the desired state in Git<\/li>\n
  2. argocd application set (Deployment): <\/strong>A controller that automatically generates and manages Argo CD Applications based on a template.<\/li>\n
  3. argocd notification<\/strong> (Deployment<\/strong>): Sends notifications about Argo CD events to various channels like email, Slack, or webhooks.<\/li>\n
  4. argocd reposerver (Deployment): <\/strong>The component that manages Git repositories and provides an API for accessing and synchronizing application manifests.<\/li>\n
  5. argocd server (Deployment): <\/strong>The main component that exposes the Argo CD API and serves the web UI for managing applications and configurations.<\/li>\n
  6. dex server (Deployment):<\/strong> It is an identity provider that can be integrated with Argo CD for user authentication and authorization with external identity providers (OIDC Providers) like GitHub, SAML etc.<\/li>\n
  7. Redis<\/strong> (Deployment)<\/strong> : Used for caching to reduce request sent to Kube API and to Git provider.<\/li>\n<\/ol>\n

    Prerequisites<\/h2>\n

    To get started with the setup, you should have the following.<\/p>\n

      \n
    1. A working Kubernetes cluster<\/a><\/li>\n
    2. Kubectl<\/a> configured with the cluster<\/li>\n
    3. Helm installed<\/a> on your workstation.<\/li>\n<\/ol>\n

      We will see about two deployment methods of Argo CD, one is using manifest and the other using Helm.<\/p>\n

      Lets get started with the setup.<\/p>\n

      Argo CD Setup Using Manifest Files<\/h2>\n

      The easiest way to set up Argo CD on Kubernetes is using plain Kubernetes manifest files available in the Argo project GitHub repository.<\/p>\n

      If you are setting up Argo CD for project requirements, use the Helm charts given in the next section.<\/p>\n

      We will deploy Argo CD in a custom namespace called argocd<\/code>.<\/p>\n

      The following kubectl commands will create the namespace and deploy the manifest.<\/p>\n

      kubectl create namespace argocd\n\nkubectl apply -n argocd --server-side --force-conflicts -f https:\/\/raw.githubusercontent.com\/argoproj\/argo-cd\/stable\/manifests\/install.yaml<\/code><\/pre>\n
      \n
      \ud83d\udca1<\/div>\n
      The server-side<\/code> flag ignores the annotation size limit because some CRDs have annotation size bigger than 262KB.<\/p>\n
      And the force-conflicts<\/code> flag prevents conflict between server-side and client-side fields by changing the ownership of fields to server-side.<\/div>\n<\/div>\n
      This command creates Kubernetes objects<\/a> related to Argo CD Namespace scoped and cluster scoped resources.<\/p>\n
      The key objects are Argocd services, deployments, and statefulsets, ClusterRoles, Configmaps, and Secrets.<\/p>\n
      It also created Argo CD custom resources like applications<\/strong>, applicationsets<\/strong> and appprojects.<\/strong><\/p>\n
      You can access the Argo CD UI in our workstation using the following port forwarding command.<\/p>\n
      kubectl port-forward svc\/argocd-server -n argocd 8080:443<\/code><\/pre>\n
      You will get an SSL error due to self-signed certificate<\/strong> added to the Argo CD server. You can click proceed to access the UI.<\/p>\n
      \"argocd<\/figure>\n
      To login to the UI, you need a username and password.<\/p>\n
      The default username is admin<\/code><\/strong>. To get the password, execute the following command.<\/p>\n
      kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath=\"{.data.password}\" | base64 --decode ; echo<\/code><\/pre>\n
      Once logged in, you will get the Argo CD server dashboard as shown below.<\/p>\n
      \"Argo<\/figure>\n
      You can clean up the setup using the following command.<\/p>\n
      kubectl delete -n argocd -f https:\/\/raw.githubusercontent.com\/argoproj\/argo-cd\/stable\/manifests\/install.yaml<\/code><\/pre>\n
      How to Deploy Argo CD Using Helm Chart<\/h2>\n
      If you are setting up Argo CD for project purposes, we highly recommend you setup using Helm charts rather than plain manifest files.<\/p>\n
      Because with plain manifest, you need to find and modify each RAW YAML file each time and re-apply it.<\/p>\n
      But with Helm, all configurations are managed in a single values file, you just need to update it and run the Helm upgrade command.<\/p>\n
      Follow the steps given below to setup Argo CD using the official Argoproject helm chart.<\/strong><\/p>\n
      Step 1: Add Argo CD repo<\/h3>\n
      Add the Argo CD repo to your system to download the Helm chart for set up.<\/p>\n
      Run the following command to add the repo.<\/p>\n
      helm repo add argo https:\/\/argoproj.github.io\/argo-helm<\/code><\/pre>\n
      Now, list every repo with the word argo using the command<\/p>\n
      helm search repo argo<\/code><\/pre>\n
      You will get the list of repos with the word argo as shown below. The chart we need is argo-cd<\/code>.<\/p>\n
      $ helm search repo argo\n\nNAME                             CHART VERSION   APP VERSION     \n\nargo\/argo                       1.0.0           v2.12.5\nargo\/argo-cd                    9.5.0           v3.3.6\nargo\/argo-ci                    1.0.0           v1.0.0-alpha2\nargo\/argo-events                2.4.21          v1.9.10\nargo\/argo-lite                  0.1.0                   \nargo\/argo-rollouts              2.40.9          v1.9.0  \nargo\/argo-workflows             1.0.7           v4.0.4  \nargo\/argocd-applicationset      1.12.1          v0.4.1 \nargo\/argocd-apps                2.0.4                   \nargo\/argocd-image-updater       1.1.5           v1.1.1  \nargo\/argocd-notifications       1.8.1           v1.2.1  \nmy-repo\/argo-cd                 11.0.0          3.1.1   \nmy-repo\/argo-workflows          13.0.6          3.7.1  \ncommunity-charts\/cloudflared    2.2.7           2026.2.0<\/code><\/pre>\n
      Step 2: Customize Helm Chart Configuration Values<\/h3>\n
      Before deploying, you need to update NodePort<\/strong> configurations in the Helm chart so that you can access Argo CD UI in the browser.<\/p>\n
      For that, use the below command to save the default values of the Helm chart in a YML file.<\/p>\n
      helm show values argo\/argo-cd > values.yaml<\/code><\/pre>\n
      Make changes in the service configuration block<\/strong>. Change the type from ClusterIP<\/strong> to NodePort<\/strong> as shown in the below image.<\/p>\n
      It is responsible for exposing the Argo CD server UI. The default nodePort is 30080<\/code>. You can customize that as well.<\/p>\n
      \"changing<\/figure>\n
      Below is the custom values file, which only has the configuration to change the service type of the Argo CD server component.<\/p>\n
      server:\n  service:\n    type: NodePort\n    nodePortHttp: 30080\n    nodePortHttps: 30443<\/code><\/pre>\n
      By changing the type to NodePort you can access Argo CD UI on the browser using the URL <Public\/Private IP of your k8s node>:<port><\/strong>.<\/p>\n
      \n
      \ud83d\udca1<\/div>\n
      Use loadbalancer to expose Argo CD in production environment<\/div>\n<\/div>\n
      Make sure to use the same node port number<\/strong> you mentioned in the values.yml<\/code><\/strong> file.<\/p>\n
      \n
      \ud83d\udca1<\/div>\n
      If you want to set up Argo CD in an private environment without access to these public registries<\/strong><\/b>, you might have to upload the image to the relevant internal registry<\/strong><\/b> and then run the helm chart with custom values.<\/div>\n<\/div>\n
      Step 3: Deploy Argo CD<\/h3>\n
      Now, use the below command to deploy Argo CD in the argocd namespace.<\/p>\n
      helm install -f values.yaml argocd argo\/argo-cd -n argocd --create-namespace<\/code><\/pre>\n
      On a successful deployment, you should see the following output.<\/p>\n
      \"argocd<\/figure>\n
      Now, run the following command to check if the pods are up and running.<\/p>\n
      $ kubectl get po -n argocd\n\nNAME                                     READY  STATUS   RESTARTS AGE\n\nargocd-application-controller-0          1\/1    Running  0        2m53s\nargocd-applicationset-controller-48css   1\/1    Running  0        2m54s\nargocd-dex-server-8f5687997-8txcr        1\/1    Running  0        2m53s\nargocd-notifications-controller-4jdd4    1\/1    Running  0        2m54s\nargocd-redis-fcd76bcfb-xnlgt             1\/1    Running  0        2m54s\nargocd-repo-server-7b8447858f-6fvsj      1\/1    Running  0        2m54s\nargocd-server-7f857f54f-5t466            1\/1    Running  0        2m54s<\/code><\/pre>\n
      All the pods are running, lets try accessing the UI.<\/p>\n
      Step 4: Log in to Argo CD Web UI<\/h3>\n
      Since we have enabled the NodePort<\/code> on 30080<\/code>, you can use the public IP or Private IP of any node of your cluster with the node port number in the format <node IP>:<port><\/strong>.<\/p>\n
      In my case, the URL will be 168.144.64.114:30080.<\/strong><\/p>\n
      Now, access the UI in your browser using the URL, you will get the following window<\/p>\n
      \"argocd<\/figure>\n
      Login to Argo CD using the username and password.<\/p>\n
      Your default username<\/strong> will be admin,<\/strong> and run the following command to get the password.<\/p>\n
      kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath=\"{.data.password}\" | base64 --decode ; echo<\/code><\/pre>\n
      This command will show your password for Argo CD, use the password and log in to Argo CD UI.<\/p>\n
      Once you log in you can see the home screen of Argo CD as shown below.<\/p>\n
      \"argocd<\/figure>\n
      Step 5: Change Default Admin Password<\/h3>\n
      We will not be using the default password for the admin user after login.<\/p>\n
      Lets, update the admin password.<\/p>\n
      The simplest way to update the password is through the UI.<\/p>\n
      From the dashboard, go to User Info and click UPDATE PASSWORD.<\/p>\n
      \"\"<\/figure>\n
      A new pop up will appear to change the password.<\/p>\n
      In there, you need to give the current and new passwords you need to update.<\/p>\n
      \"\"<\/figure>\n
      Then click the SAVE NEW PASSWORD button to update the new password.<\/p>\n
      That’s it, you will get a password update successful message after a successful update.<\/p>\n
      The other method for updating a password and managing users is done using the ArgoCD CLI.<\/p>\n
      Refer to the user management<\/a> blog for more information about user management.<\/p>\n
      Deploying Applications on GitHub using Argo CD (GitOps Way)<\/h2>\n
      Now that we have the Argo CD setup ready, we can test an Nginx deployment that shows a custom message on the index page exposed on NodePort 32000.<\/p>\n
      We have the Nginx deployment files in the Argo CD Guide repository.<\/a><\/p>\n
      git clone https:\/\/github.com\/techiescamp\/argocd-guide.git\n\ncd argocd-guide\/nginx-deployment<\/code><\/pre>\n
      You can see the manifests are organized under the nginx-deployment<\/code> folder as shown below.<\/p>\n
      \u279c  nginx-deployment\n      \u251c\u2500\u2500 configmap.yaml\n      \u251c\u2500\u2500 deployment.yaml\n      \u2514\u2500\u2500 service.yaml<\/code><\/pre>\n
      From the Argo CD dashboard press the + NEW APP<\/strong> button to configure the repository.<\/p>\n
      \"create<\/figure>\n
      A new window will pop up, specify the Application Name as nginx-deployment<\/strong>, give the Project Name as default<\/code>, and set the SYNC POLICY to automatic or manual as you like.<\/p>\n
      If you set the SYNC POLICY<\/code> to automatic, Argo CD automatically detects the changes made in your Git repository and triggers the deployment, or if you set the SYNC POLICY to manual you have to trigger it manually to start the deployment.<\/p>\n
      By default the automatic sync uses polling<\/strong> to find the changes that happens in the git repository. The default polling interval is three minutes (180 seconds)<\/strong>. It is a configurable option in the helm chart. You can modify timeout.reconciliation<\/code> as per your sync requirement.<\/p>\n
      Also enable AUTO-CREATE NAMESPACE<\/strong> option so that namespace will be created if it doesn’t exist.<\/p>\n
      \"create<\/figure>\n
      Also, there are other SYNC POLICY options, enable them as per your need.<\/p>\n
      Now, add the source information which is your Git repository URL, and the path of the YAML file.<\/p>\n
      \"create<\/figure>\n
      Then, select the Cluster URL,<\/strong> which will be shown when you select the Cluster URL tab. Select https:\/\/kubernetes.default.svc<\/code> as we are deploying the application on the same cluster where Argo CD is deployed.<\/p>\n
      Also specify the namespace as webserver<\/strong>. Then, click the Create button <\/strong>as shown below.<\/p>\n
      \"create<\/figure>\n
      When you click the create button it will sync the repository manifests and deploy it.<\/p>\n
      You can see the deployment information in the dashboard as shown below.<\/p>\n
      \"application<\/figure>\n
      Click the application to see detailed info about your deployment as shown below.<\/p>\n
      \"application<\/figure>\n
      To validate our deployment, lets try to access the Nginx deployment on NodePort 32000. You should see a page as shown below.<\/p>\n
      \"accessing<\/figure>\n
      How to Configure GitHub Webhook for Argo CD?<\/h2>\n
      Even though Argo CD continuously monitors Git for changes<\/strong> there is a time delay in syncing the changes.<\/p>\n
      To remove the time delay we can use webhook which triggers the sync process as soon as a change is made in Git.<\/p>\n
      Let’s look at how to configure a webhook on Argo CD.<\/p>\n
      First, go to your Git repository which you configured with Argo CD then go to<\/p>\n
      Setting->Webhooks->Add webhook<\/strong> as shown in the <\/strong>below image to configure webhooks.<\/p>\n
      \"\"<\/figure>\n
      After pressing the Add webhook button you can see the configuration window as shown below.<\/p>\n
      The Payload URL would be the Argo CD webUI endpoint appended with \/api\/webhook<\/strong>. That is <node IP>:<port>\/api\/webhook<\/strong><\/p>\n
      For example, https:\/\/34.71.163.101:30080\/api\/webhook.<\/strong><\/p>\n
      Change the Content type<\/strong> to application\/json<\/strong>, and give the Secret<\/strong> as you like.<\/p>\n
      \"configure<\/figure>\n
      Now, select Enable SSL verification if you are using an SSL certificate for your Argo CD, and select Disable if you are not using an SSL certificate.<\/p>\n
      Then select the event in which you like to trigger the webhook, it will trigger the webhook according to the event you select.<\/p>\n
      \"\"<\/figure>\n
      Click the Add webhook <\/strong>button to add the webhook configuration for your Argo CD, you can see the webhook has been added as shown below.<\/p>\n
      \"argocd<\/figure>\n
      By selecting it you can see the triggers made by the hook as shown below.<\/p>\n
      \"argocd<\/figure>\n
      Clean UP<\/h2>\n
      If you no longer need the setup, run the following command.<\/p>\n
      helm delete argocd -n argocd<\/code><\/pre>\n
      Argo CD Setup Best Practices<\/h2>\n
      Following are some of the best practices you need to follow when running Argo CD for production use cases.<\/p>\n
        \n
      1. It is a standard practice to run one Argo CD instances per environment (dev, stage, prod) to avoid potential conflicts.<\/li>\n
      2. Ensure you enable RBAC to limit access to the Argo CD instance to follow the principle of least privilege. Categorize users based on roles and responsibilities and audit them regularly.<\/li>\n
      3. Patch the Argo CD image regularly to avoid security vulnerabilities.<\/li>\n
      4. Backup Argo CD configuration for disaster Recovery and backup purposes.<\/li>\n
      5. Setup monitoring and alerting using tools like Prometheus<\/a> for events like deployment <\/a>failures, resource constraints, etc.<\/li>\n<\/ol>\n
        Argo CD Configuration FAQ’s<\/h2>\n
        How does Argo CD store data?<\/h3>\n
        Since Argo CD is a stateless app, it doesn’t need any volumes to store data. All the data is stored as Kubernetes Objects<\/a>. So ultimately, all the Argo CD data is stored in Kubernetes etcd. Also, it uses Redis as a throwaway cache.<\/p>\n
        If you want a study guide for Certified Argo Project Associate (CAPA), then here is the detailed study guide<\/a>.<\/p>\n
        How to change the default admin password in Argo CD?<\/h3>\n
        You can either update the password from the Argo CD UI or use Argo CD CLI commands to update it.<\/p>\n
        Conclusion<\/h2>\n
        In summary, we have seen about deploying Argo CD using both the manifest method and the Helm method.<\/p>\n
        Also, we tested Argo CD by deploying an application manifest on GitHub in a GitOps way and configured a webhook for the repository.<\/p>\n
        \n
        Ngu\u1ed3n:<\/strong> How to Deploy Argo CD on Kubernetes: A Beginner's Guide \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
        Source: https:\/\/devopscube.com\/setup-argo-cd-using-helm\/<\/p>\n","protected":false},"author":1,"featured_media":272,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-271","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\/271","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=271"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/271\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/272"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=271"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=271"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=271"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}