Skip to main content

ArgoCD

Automation is key to efficient deployment management. Deployment automation addresses common challenges: managing releases, tracking code changes, and maintaining Kubernetes cluster resources becomes complex at scale. ArgoCD automates deployments once a Kubernetes cluster is configured, providing security through consistent updates with minimal downtime. ArgoCD manages deployment versions by modifying manifests—YAML documents that define how applications are deployed to Kubernetes clusters.

Installation​

The simpliest method to install ArgoCD is through the Helm package manager which you can access via OpenLens. Before we begin, add the namespace argocd to the cluster.

Namespace

In Helm Charts, search for argo-cd and select 'Install'

ArgoCD

Change the namespace to argocd and select 'Install'

ArgoCDNamespace

ArgoCD Login Secret​

To get the user login for argocd, navigate to Config > Secrets. Change the namespace to argocd. For the secrets window, select argocd-secret. Select the closed eyes button and get the 'clearPassword'. Combined with username 'admin', this will be the login for the dashboard.

ArgoCD Secret

Accessing The Dashboard​

To expose the ArgoCD service on the network, navigate to Network > Services, change the namespace to argocd, and locate the service containing http. Select and edit the service configuration:

spec:
  ports:
    - name: http
      protocol: TCP
      port: 80
      targetPort: http
    - name: https
      protocol: TCP
      port: 443
      targetPort: http
  selector:
    app.kubernetes.io/component: server
    app.kubernetes.io/instance: argo-cd-1729881606
    app.kubernetes.io/name: argo-cd
  clusterIP: 10.43.157.82
  clusterIPs:
    - 10.43.157.82
  type: ClusterIP
  sessionAffinity: None
  ipFamilies:
    - IPv4
  ipFamilyPolicy: SingleStack
  internalTrafficPolicy: Cluster

Change it to NodePort and add nodePort to the port options. This port needs to be with the range of 30000 and 32767.

spec:
  ports:
    - name: http
      protocol: TCP
      port: 80
      targetPort: http
      nodePort: 30000
    - name: https
      protocol: TCP
      port: 443
      targetPort: http
      nodePort: 30001
  selector:
    app.kubernetes.io/component: server
    app.kubernetes.io/instance: argo-cd-1729881606
    app.kubernetes.io/name: argo-cd
  clusterIP: 10.43.157.82
  clusterIPs:
    - 10.43.157.82
  type: NodePort
  sessionAffinity: None
  ipFamilies:
    - IPv4
  ipFamilyPolicy: SingleStack
  internalTrafficPolicy: Cluster

Now this is all good except by default, all connections will be secure so we need to adjust it. On each of the Kubernetes servers (just the main node), create a file called insecurePatch.yaml with the following:

apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-cmd-params-cm
  namespace: argocd
data:
  server.insecure: "true"

Now run the command:

kubectl apply -f insecurePatch.yaml

Now open a browser session and navigate to kubernetesIPAddress:30000

You may get the following error which you will have to bypass.

notPrivate

bypass notPrivate

From there you can log into ArgoCD.

Obtaining SSH Keys​

In order for argoCD to work with our workflows including having automation, it will need to be able to access our Git repositories and the only way it can do that is if we configure the SSH protocols for it. On the Kubernetes server nodes, ssh into the computer and run the following:

ssh-keygen -t rsa -b 4096

This will create two files in ~/.ssh called id_rsa and id_rsa.pub. Retrieve the public keys by running:

cat ~/.ssh/id_rsa.pub

Configure SSH Public Keys on GitHub​

With the two keys, navigate to settings:

GitHub Settings

Open SSH and GPG keys and select 'New SSH Key':

new SSH

Copy the public keys into the settings and apply them.

SSH and GPG Keys

Create ArgoCD manifest​

ArgoCD are manifests stored on GitHub so ArgoCD knows how to deploy containers. So on GitHub, we will create a few repositories and configure them to work on ArgoCD. For this example, we will create a git repository called argocd-services. Once created, we need to go to Settings > Actions > General and make sure we set Workflow permissions to 'Read and write permissions'. This is important as later, we will use GitActions on code repositories to build and push versions automatically. On build, these versions will update build tags as well as update the ArgoCD manifests telling kubernetes to update the container to the latest code.

Repository Settings