Skip to main content
With cluster monitoring in place, the next step is continuous deployment. In this guide we install ArgoCD using Glasskube and verify access to its web UI. ArgoCD provides GitOps-driven continuous delivery: it continuously monitors Git repositories containing Kubernetes manifests or Helm charts and reconciles the cluster to match the desired state stored in Git.
The image is a diagram depicting a single-node Kubernetes cluster with continuous deployment using Argo CD, showing applications A and B within different namespaces.

​
Why ArgoCD?

ArgoCD is a cluster-scoped GitOps controller that acts as the continuous-deployment engine for Kubernetes. It is designed to:
  • Continuously compare cluster state to Git and apply changes automatically.
  • Provide a web UI for visualizing and managing applications.
  • Support declarative application definitions (manifests, Helm, Kustomize, etc.).
Package characteristics for this installation are summarized below.
The image describes a tool for deploying GitOps definitions, highlighting four features: cluster scoped, no value definition, has an entry point, and no dependencies.

​
Install ArgoCD using Glasskube CLI

Use the Glasskube CLI to install ArgoCD into your cluster. The example below demonstrates a typical interactive installation session.
Glasskube will add ArgoCD into the argocd namespace (or the namespace configured by Glasskube). After installation, ArgoCD exposes a web UI that you can open via the Glasskube dashboard.

​
Retrieve the initial admin password

ArgoCD generates a one-time admin password at installation. Retrieve it with the argocd CLI:
Sample output (your password will differ):
Log in with username admin and the printed initial password. After logging in, immediately update the password:
You can also authenticate via the CLI (adjust host/port if you’re using port-forwarding or a custom ingress):
For production environments: serve the ArgoCD UI over HTTPS, rotate the default admin password immediately, and consider integrating Single Sign-On (SSO) and role-based access controls. Also restrict UI access using network policies or an authenticated ingress.

​
Access the ArgoCD dashboard via Glasskube

After installation and authentication, open the ArgoCD entry point from the Glasskube dashboard. In local setups you may need to accept a browser security exception when using HTTP or a self-signed certificate.
The image shows a user interface for a software platform called Glasskube, featuring a grid of Kubernetes-related packages available for installation or opening. There are options like Argo CD, cert-manager, and Kubernetes dashboard.
If you expose ArgoCD directly (NodePort/LoadBalancer) for testing, ensure you secure the endpoint. Avoid leaving the initial admin password unchanged or exposing the UI without authentication in non-development environments.

​
Next steps

  • Connect ArgoCD to your application Git repositories and create Application resources (manifests, Helm charts, or Kustomize overlays).
  • Configure automated sync and health checks for GitOps-driven rollouts.
  • Integrate ArgoCD with observability and alerting systems for deployment monitoring.
Useful references:

Watch Video