Setting Up ArgoCD on Kubernetes: A Quick Guide

ArgoCD is a popular GitOps continuous delivery tool that simplifies Kubernetes application deployments. In this article, I’ll guide you through the basic steps to install ArgoCD using Helm, configure access for both external and internal environments, and ensure your KUBECONFIG is set correctly.

Step 1: Ensure KUBECONFIG is Properly Configured

Before starting, make sure your KUBECONFIG environment variable points to the correct Kubernetes cluster configuration file. This file allows kubectl and other tools to interact with your cluster.

Save and reload your shell configuration:

source ~/.bashrc

Append the following line:

export KUBECONFIG=/path/to/your/kubeconfig.yaml

If not set, add the correct path to your ~/.bashrc file (for Bash users):

nano ~/.bashrc

Check if KUBECONFIG is set:

echo $KUBECONFIG

This ensures your tools can correctly access your Kubernetes cluster.

Step 2: Install ArgoCD Using Helm

Helm simplifies the deployment of Kubernetes applications by packaging them into reusable charts. To install ArgoCD:

• -n argocd: Specifies the namespace argocd where ArgoCD will be installed.
• --create-namespace: Creates the namespace if it doesn’t exist.

Verify the installation:

kubectl get all -n argocd

Add the ArgoCD Helm repository:

helm repo add argo https://argoproj.github.io/argo-helm
helm repo update

Install ArgoCD:

helm install argocd argo/argo-cd -n argocd --create-namespace

This command lists all ArgoCD-related resources, ensuring the installation is complete.

Step 3: Configure Access to ArgoCD

ArgoCD’s default installation provides internal access. You can expose the ArgoCD UI for external or internal use by modifying the service type.

Option 1: Using Ingress (External Access)

1. Apply a DNS record to point argocd.example.com to your ingress controller.
2. Test access by visiting https://argocd.example.com.

Update the service configuration to use an ingress controller (e.g., Traefik or NGINX). For example:

annotations:
  kubernetes.io/ingress.class: "nginx"
spec:
  rules:
  - host: argocd.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: argocd-server
            port:
              number: 80

Edit the argocd-server service to configure ingress:

kubectl edit svc argocd-server -n argocd

Option 2: Using NodePort (External or Internal Access)

If you don’t have an ingress controller or need simpler access, change the service type to NodePort:

Access ArgoCD via:

http://<node-ip>:<node-port>

Retrieve the NodePort and access ArgoCD:

kubectl get svc argocd-server -n argocd

Look for the NodePort value under the PORT(S) column (e.g., 30000-32767).

Update the service type to NodePort:

spec:
  type: NodePort

Edit the service type:

kubectl edit svc argocd-server -n argocd

以上資訊ChatGPT整理