Are you getting “Invalid username or password” while trying to log in to ArgoCD as admin?
In this article, I’ll walk you through the process of resetting the ArgoCD admin password.
Whether you’ve forgotten the ArgoCD admin password or need to update it for security reasons, these clear instructions will help you get back in control. (more…)
An ArgoCD CLI is the official command-line interface for an ArgoCD.
It can be used to interact with the ArgoCD API server and manage ArgoCD applications.
In this post I will show how to download and install the latest stable version of the ArgoCD CLI on Windows through a graphical user interface (GUI), or using a command-line prompt (CMD) or PowerShell. (more…)
In ArgoCD, if you try to add/update some object that already exists, you my receive an error as follows:
Unable to connect repository: existing repository spec is different; use upsert flag to force update.
If you try to create/update an existent application, cluster or any other object you will receive the similar error. (more…)
In an ArgoCD’s user interface (UI), if you select a connection method “VIA HTTPS” and try to add a private repository, despite the fact that you’ll get a message “Successfully updated <repoURL> repository”, the actual repository connection status may be marked as ❌ Failed.
The reason of this may be in a self-signed certificate, or a certificate signed by a custom Certificate Authority (CA).
This post shows how to fix the “x509: certificate signed by unknown authority” error while adding the private repository in ArgoCD. (more…)
While trying to communicate with an ArgoCD server over a command-line interface (CLI), you may receive an error as follows: “FATA[0005] rpc error: code = Unauthenticated desc invalid session: signature is invalid“.
This error usually occurs when you have forgotten to login to the ArgoCD server.
This short post shows how to resolve the ArgoCD’s “FATA[0005] Unauthenticated” error. (more…)
While trying to delete an ArgoCD application through a user interface (UI) you may receive an error as follows:
Unable to delete application: error patching application with finalizers: Application.argoproj.io “<appName>” is invalid: metadata.finalizers: Forbidden: no new finalizers can be added if the object is being deleted, found new finalizers []string{“resources-finalizer.argocd.argoproj.io”} .
To force the deletion of the ArgoCD application that is stuck, you can either use an argocd or kubectl commands as showing in the post below. (more…)
While trying to log in to the ArgoCD server from a command-line interface (CLI), the connection attempt may hang for some time and then fail with the error as follows: “FATA[0060] context deadline exceeded“.
This error usually occurs when the ArgoCD instance is setup behind a load balancer or reverse proxy which doesn’t support HTTP2.
Besides of this, the argocd login command may hang for no apparent reason while testing whether the server is configured with TLS.
This short note shows how to resolve these issues. (more…)
The first time you deploy an ArgoCD application to a Kubernetes cluster, it creates an initial default administrator account, that can be used to access the ArgoCD using a user interface (UI) or over a command-line interface (CLI).
The ArgoCD stores the initial password for the default admin account in a Kubernetes Secret resource, named argocd-initial-admin-secret.
This short note shows how to get the default (initial) admin password for the ArgoCD. (more…)