ArgoCD installation methods¶

ArgoCD is a declarative, GitOps continuous delivery tool for Kubernetes.^[400-devops-04-ci-cd-pipelines-argocd.md] The following methods are available for accessing the ArgoCD server interface after installation, primarily focusing on network exposure via the Kubernetes Service.

Service Exposure via LoadBalancer¶

To make the ArgoCD server accessible externally through a load balancer, the service type must be patched.^[400-devops-04-ci-cd-pipelines-argocd.md] This involves modifying the argocd-server service specification in the argocd namespace.

[kubectl](<./kubectl.md>) patch svc argocd-server -n [ArgoCD](<./argocd.md>) -p '{"spec": {"type": "LoadBalancer"}}'

Service Exposure via Port Forwarding¶

For local access or testing, kubectl port-forward can be used to tunnel traffic to the ArgoCD server.^[400-devops-04-ci-cd-pipelines-argocd.md] This forwards a local port (e.g., 8080) to the service's port (443) within the cluster.

[kubectl](<./kubectl.md>) port-forward svc/argocd-server -n [ArgoCD](<./argocd.md>) 8080:443

Credential Retrieval¶

The initial admin password is stored in a Kubernetes Secret.^[400-devops-04-ci-cd-pipelines-argocd.md] To retrieve the decoded password for the first login, the following command can be used:

[kubectl](<./kubectl.md>) -n [ArgoCD](<./argocd.md>) get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d; echo

Sources¶

• 400-devops-04-ci-cd-pipelines-argocd.md