{"id":402,"date":"2024-04-25T11:39:01","date_gmt":"2024-04-25T11:39:01","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=402"},"modified":"2024-04-25T11:39:01","modified_gmt":"2024-04-25T11:39:01","slug":"configure-multiple-kubernetes-clusters-argo-cd","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=402","title":{"rendered":"How to Configure Multiple Kubernetes Clusters on ArgoCD"},"content":{"rendered":"

In this blog, you will learn how to configure and manage multiple Kubernetes clusters using Argo CD with step-by-step instructions.<\/p>\n

Argo CD<\/a> is a CD tool that has an amazing feature called multi-cluster support,<\/strong> which means you can deploy and manage applications not only in the cluster where Argo CD is installed but also in other external clusters.<\/p>\n

Argo CD will act as a central hub for every cluster, and Argo CD continuously sends API calls to every available cluster to keep them in sync and to check their health status.<\/p>\n

There is no specific limit to adding clusters to Argo CD. However, the cluster where Argo CD is deployed should have the required resources to handle the API calls sent and received from other clusters configured to it.<\/p>\n

The image below shows the two methods we can use to add a cluster to Argo CD.<\/p>\n

\"Argo<\/figure>\n

Setup Prerequisites<\/h2>\n

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

    \n
  1. A running Argo CD setup<\/a><\/li>\n
  2. Kubernetes Clusters<\/a> with permission to create ClusterRole<\/li>\n
  3. Argo CD CLI<\/a><\/li>\n
  4. Kubectl<\/a> is configured on your workstation.<\/li>\n<\/ol>\n

    Configuring Multiple Clusters to Argo CD<\/h2>\n

    To configure multiple clusters in Argo CD there are primarily two methods. They are<\/p>\n

      \n
    1. Using Argo CD Custom Resource Definitions (CRD)<\/li>\n
    2. Using Argo CD CLI With Kubecofig files<\/li>\n<\/ol>\n

      Let’s look at each method in detail.<\/p>\n

      Method 1: Argo CD CRD Method<\/h3>\n

      Let’s see how to add multiple Kubernetes clusters to Argo CD using the CRD method.<\/p>\n

      For the setup, I am using three Kubernetes Clusters. One Cluster has Argo CD installed, and the other two clusters will be added to Argo CD using the CRD method.<\/p>\n

      Follow the below steps to add multiple clusters to Argo CD using the CRD method.<\/p>\n

      In the below steps, do Step 1 and Step 2 on the clusters you are going to add to the Argo CD and Step 3 in the Argo CD cluster.<\/p>\n

      Step 1: Create a Service Account<\/h4>\n

      First, log in to Cluster which you need to add to Argo CD and start the RBAC configuration, create a YAML file, and copy the below content<\/p>\n

      apiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: argocd-manager\n  namespace: kube-system\n---\napiVersion: rbac.authorization.k8s.io\/v1\nkind: ClusterRole\nmetadata:\n  name: argocd-manager-role\nrules:\n- apiGroups:\n  - '*'\n  resources:\n  - '*'\n  verbs:\n  - '*'\n- nonResourceURLs:\n  - '*'\n  verbs:\n  - '*'\n---\napiVersion: rbac.authorization.k8s.io\/v1\nkind: ClusterRoleBinding\nmetadata:\n  name: argocd-manager-role-binding\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: ClusterRole\n  name: argocd-manager-role\nsubjects:\n- kind: ServiceAccount\n  name: argocd-manager\n  namespace: kube-system<\/code><\/pre>\n
      This file will create a serviceaccount, a clusterrole with full cluster privileges, and bind the clusterrole to the serviceaccount.<\/p>\n
      We are giving full cluster privileges because Argo CD needs full privileges on the cluster to create, delete, and manage applications on any namespace with the required resources.<\/p>\n
      Step 2: Create a Secret<\/h4>\n
      The next step is to create the Bearer Token and configure it to the service account we created in Step 1.<\/p>\n
      Create another YAML file and copy the content below. This will create a token for the service account argocd-manager<\/code>.<\/p>\n
      apiVersion: v1\nkind: Secret\nmetadata:\n  name: argocd-manager-token\n  namespace: kube-system\n  annotations:\n    kubernetes.io\/service-account.name: argocd-manager\ntype: kubernetes.io\/service-account-token<\/code><\/pre>\n
      Once the secret has been created save the token and CA certificate as variables so that we can use them in the next step.<\/p>\n
      Run the following command to save the bearer token and CA certificate as a variable<\/p>\n
      ca=$(kubectl get -n kube-system secret\/argocd-manager-token -o jsonpath='{.data.ca\\.crt}')\n\ntoken=$(kubectl get -n kube-system secret\/argocd-manager-token -o jsonpath='{.data.token}' | base64 --decode)<\/code><\/pre>\n
      Step 3: Create a Secret in the Argo CD Cluster<\/h4>\n
      To complete the RBAC configuration, log in to the Argo CD cluster and create a Secret with the data Argo CD needs to connect with other clusters.<\/p>\n
      Run the following command to create the secret<\/p>\n
      cat <<EOF | kubectl apply -n argocd -f -\napiVersion: v1\nkind: Secret\nmetadata:\n  name: cluster1-secret\n  labels:\n    argocd.argoproj.io\/secret-type: cluster\ntype: Opaque\nstringData:\n  name: cluster-1\n  server: https:\/\/B66A3A2BB2.**************\n  config: |\n    {\n      \"bearerToken\": \"${token}\",\n      \"tlsClientConfig\": {\n        \"serverName\": \"B66A3A2BB2.************\",\n        \"caData\": \"${ca}\"\n      }\n    }\nEOF<\/code><\/pre>\n
      In this command, make sure to update your cluster endpoint in the above command.<\/p>\n
      Also, you can see it gets the bearer token and CA certificate from the variable we created in Step 2.<\/p>\n
      Repeat the same steps to the cluster you need to add to Argo CD and change the secret name and cluster name when configuring the other clusters.<\/p>\n
      Once you have run the above command, if you check under the option Setting->Clusters<\/strong> on Argo CD UI, you can see a new cluster as shown below<\/p>\n
      \"new<\/figure>\n
      If you want to deploy an application on the new cluster, you can select between clusters while adding a NEW APP<\/strong> as shown below<\/p>\n
      \"Argo<\/figure>\n
      After selecting the NEW APP<\/strong> button a new page will open, scroll down to the DESTINATION<\/strong> tag where you can select between available clusters as shown below<\/p>\n
      \"selecting<\/figure>\n
      Using the DESTINATION<\/strong> tab you can select the cluster in which you want to deploy the application using Argo CD.<\/p>\n
      \"application<\/figure>\n
      You can see in the above image the two applications are deployed in two different clusters.<\/p>\n
      Method 2: Using Argo CD CLI with Kubeconfig File<\/h3>\n
      You can also configure multiple clusters from the Kubeconfig file<\/a> you have on your workstation assuming you have the Argo CD CLI configured on your system.<\/p>\n
      Argo CD CLI can read the contexts from the Kubeconfig file and use the credentials from the Kubeconfig.<\/p>\n
      For the setup, I am using two AWS EKS clusters from the same account, you can use the cluster of any Cloud platform.<\/p>\n
      Step 1: Login to Argo CD<\/h4>\n
      Make sure that you have updated the cluster details to the kubeconfig<\/strong> file and logged into Argo CD using Argo CD CLI, if not run the following command to log in to Argo CD.<\/p>\n
      argocd login <url>:<port> --username <username> --password <password><\/code><\/pre>\n
      With this command, you can log in to Argo CD using the username and password.<\/p>\n
      Step 2: Get the Context of the Cluster<\/h4>\n
      Once you have logged in to Argo CD, you need to find the context of the cluster you need to add to Argo CD.<\/p>\n
      Run the following command to get the context from the kubeconfig<\/strong> file<\/p>\n
      kubectl config get-contexts -o name<\/code><\/pre>\n
      You will get the list of cluster contexts that are configured in the kubeconfig file.<\/p>\n
      Step 3: Add the Cluster<\/h4>\n
      To add the cluster to Argo CD, use the context of the running cluster you got from the previous step on the below command<\/p>\n
      argocd cluster add --kubeconfig <path-of-kubeconfig-file> --kube-context string <cluster-context> --name <cluster-name><\/code><\/pre>\n
      Make sure to add the cluster context in the above command.<\/p>\n
      This command will create a service account Argo CD-manager<\/strong> on the cluster you specify in the above command with full cluster privileges, so make sure you have the required permissions on the cluster.<\/p>\n
      If adding the cluster to Argo CD is successful you will get the following output in return<\/p>\n
      \"output<\/figure>\n
      After getting the above output, you can see a new cluster has been added to Argo CD in the UI.<\/p>\n
      Conclusion<\/h2>\n
      In this blog, you learned two methods of adding multiple clusters to Argo CD, one is using the Argo CD CRD method, and another method is using Argo CD CLI.<\/p>\n
      I hope you find this blog useful for adding multiple clusters to Argo CD using simple steps.<\/p>\n
      If you face any issues during the configuration, do let us know in the comments section. We will take a look.<\/p>\n
      \n
      \ud83c\udf81<\/div>\n
      Bonus:<\/strong><\/b> Here is a free study guide for Certified Argo Project Associate (CAPA)<\/a>.<\/div>\n<\/div>\n
      \n
      Ngu\u1ed3n:<\/strong> How to Configure Multiple Kubernetes Clusters on ArgoCD \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
      Source: https:\/\/devopscube.com\/configure-multiple-kubernetes-clusters-argo-cd\/<\/p>\n","protected":false},"author":1,"featured_media":403,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-402","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\/402","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=402"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/402\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/403"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=402"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=402"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=402"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}