¶
ArgoCD installation workflow¶
The ArgoCD installation workflow describes the steps required to deploy ArgoCD onto a Kubernetes cluster and access its web interface.^[400-devops-04-ci-cd-pipelines-devops-ci-github-action-argocd-app-config-readme.md]
Installation¶
To install ArgoCD, a dedicated namespace is created first, followed by the application of the official installation manifest^[400-devops-04-ci-cd-pipelines-devops-ci-github-action-argocd-app-config-readme.md].
[kubectl](<./kubectl.md>) create namespace [ArgoCD](<./argocd.md>)
[kubectl](<./kubectl.md>) apply -n [ArgoCD](<./argocd.md>) -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
Access¶
Once installed, the ArgoCD UI is accessed locally by forwarding the argocd-server service port^[400-devops-04-ci-cd-pipelines-devops-ci-github-action-argocd-app-config-readme.md].
[kubectl](<./kubectl.md>) port-forward svc/argocd-server 8080:443 -n [ArgoCD](<./argocd.md>)
Authentication¶
The initial admin password is stored in a Kubernetes Secret named argocd-initial-admin-secret^[400-devops-04-ci-cd-pipelines-devops-ci-github-action-argocd-app-config-readme.md].
[kubectl](<./kubectl.md>) -n [ArgoCD](<./argocd.md>) get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 --decode && echo
For security, it is recommended to change or delete this initial password after the first login^[400-devops-04-ci-cd-pipelines-devops-ci-github-action-argocd-app-config-readme.md].
Related Concepts¶
Sources¶
^[400-devops-04-ci-cd-pipelines-devops-ci-github-action-argocd-app-config-readme.md]