Managing the cluster in ArgoCD

Overview

ArgoCD is a declarative, GitOps continuous delivery tool for Kubernetes. It is designed as a Kubernetes controller that continuously monitors UiPath® running applications and checks the current state against the desired target state as specified in the docker registry. For more details, see ArgoCD documentation.

Administrators can have an overview of the cluster, configurations, applications status, and health, all via a simple UI or CLI. ArgoCD comes with its own open-source bundled Redis, which supports both HA and non-HA configurations.

Automation Suite uses ArgoCD in the following scenarios:

• Installing and upgrading the Fabric components and core UiPath® services.
• Automating the deployment of the desired application states in the specified target environments. ArgoCD follows the GitOps pattern of using Git/helm repositories as the source of truth for defining the desired application state.
• Keeping track of the installation state. If the installation failed at a specific point and you resume it after a while, ArgoCD skips all the steps that are already synced and resumes from the point where it failed.
• Self-healing the applications. If you mistakenly delete any of the objects, the manifests will automatically get synced.

ArgoCD read-only scenarios

You can use the ArgoCD account in the following read only scenarios:

• Visualizing all your apps, pods, and services in a simple interface
• Monitoring the health of all your apps, pods, and services
• Quickly identifying issues in your deployment
• Resyncing your application in your cluster

ArgoCD advanced scenarios

Important: You must not modify any other settings or parameters except for the ones listed in this section.

You can use the ArgoCD admin account in the following advanced scenarios:

• Changing parameters for debugging purposes only; for instance, disabling self-healing;
• Deleting pods;
• Troubleshooting;
• Managing Orchestrator custom configuration; for instance, setting up encryption key per tenant;
• Updating the database connection strings;
• Syncing applications.
  Note: Make sure to refer to the proper UiPath® documentation before deleting or changing the advanced configuration on the UI.

Accessing ArgoCD

To log into your ArgoCD instance, follow the steps outlined in the scenario that applies to your specific case:

• If you have a dedicated ArgoCD instance, see Accessing the dedicated ArgoCD instance.

• If you use a shared ArgoCD instance, see Accessing the shared ArgoCD instance.