testing argocd

from the k8s client system

server install

as mentioned in the guide

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

kubectl get svc -o wide -n argocd | grep ^argocd-server
kubectl patch svc argocd-server -n argocd -p '{"spec": {"type": "NodePort"}}'
# -p '{"spec": {"type": "LoadBalancer"}}'

client install

grab the latest binary

==> Assets / argocd-linux-amd64

wget https://github.com/argoproj/argo-cd/releases/download/v2.10.4/argocd-linux-amd64
chmod +x argocd-linux-amd64
mv -i argocd-linux-amd64 /usr/local/bin/argocd
which argocd
argocd version

client usage

you need to login first

#minikube service list | grep https

#argocd admin initial-password -n argocd --server 192.168.49.2:31042 --plaintext --plaintext
argocd admin initial-password -n argocd --core

#argocd account update-password

#argocd login 192.168.49.2:31042
argocd login --core

ready to go

assuming remote minikube system

find the service to tunnel

minikube service list | grep https

# argocd http redirects to https
ssh bravo17 -L 8443:192.168.49.2:31872

reach the UI

https://localhost:8443/

resources

client install

https://argo-cd.readthedocs.io/en/stable/cli_installation/

server install

https://argo-cd.readthedocs.io/en/stable/operator-manual/ingress/ ==> serve argocd with ingress

https://www.digitalocean.com/community/tutorials/how-to-deploy-to-kubernetes-using-argo-cd-and-gitops