How to log on to the GitOps system - Container Service for Kubernetes

Describes how ACK One GitOps users log on to the GitOps system using the Argo CD CLI or web UI.kubectl port-forward.

Access mode	When to use
Load balancer IP	The Argo CD server is exposed via a load balancer and you need direct, persistent access
`kubectl port-forward`	You need temporary local access without exposing the server externally

Prerequisites

Before you begin, ensure that you have:

kubectl is connected to the Fleet instance using the kubeconfig from the ACK One console
GitOps enabled for the Fleet instance in ACK One
Argo CD CLI v2.8.7 is installed from Argo CD v2.8.7 (CLI access only)

Log on using the Argo CD CLI

Access via load balancer IP

Get the load balancer IP of the Argo CD server.

kubectl get svc -nargocd argocd-server -ojsonpath='{.status.loadBalancer.ingress[0].ip}'

Get the initial admin password.

kubectl -nargocd get secret argocd-initial-admin-secret -ojsonpath='{.data.password}' |base64 -d

Log on to the Argo CD server.

argocd login <argocd-server-load-balancer-ip>
Username: admin
Password:
'admin:login' logged in successfully
Context '<argocd-server-load-balancer-ip>' updated

Access via port forwarding

Log on as a local user through port forwarding.

export ARGOCD_OPTS='--port-forward-namespace argocd --port-forward'

argocd login
Username: localuser1
Password:
'localuser1:login' logged in successfully
Context 'port-forward' updated

Log on using the Argo CD UI

Access via load balancer IP

Go to https://<argocd-server-load-balancer-ip> in your browser.
On the logon page, enter the local user's username and password, then click SIGN IN.

Access via port forwarding

Use the fleet KubeConfig on your local machine to set up a port-forward proxy, then access the Argo CD UI through the proxy.
```
kubectl port-forward -n argocd service/argocd-server 8080:https
```
Go to https://127.0.0.1:8080 in your browser.
On the logon page, enter the local user's username and password, then click SIGN IN.