- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to Troubleshoot Services During Installation
- How to Uninstall the Cluster
- How to clean up offline artifacts to improve disk space
- How to disable TLS 1.0 and 1.1
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bucket
- How to debug failed Automation Suite installations
- How to disable TX checksum offloading
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Kinit: Cannot Find KDC for Realm <AD Domain> While Getting Initial Credentials
- Kinit: Keytab Contains No Suitable Keys for *** While Getting Initial Credentials
- GSSAPI Operation Failed With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis Probe Failure
- RKE2 Server Fails to Start
- Secret Not Found in UiPath Namespace
- ArgoCD goes into progressing state after first installation
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs

Automation Suite installation guide
Glossary
linkNode
linkAny bare-metal or virtual machine on which you can install Automation Suite.
Kubernetes Cluster
linkA set of nodes that host containerized applications.
Provider
linkA service or API required by an application to function. It is a generalization of the ArgoCD application, as it may not necessarily result in an actual deployment, but only in a configuration to an external system. For example: an object store can be an internal Ceph application, or an external S3 bucket provided by MinIO.
Dependency
linkA relationship between two ArgoCD applications, where one requires the other in order to function.
Fabric Stage
linkA step in the installation process where fabric applications are installed.
Resource Utilization
linkThe resource consumption of a product during its usage.
Resource Request
linkThe machine resources (CPU, memory) a product needs for an optimal installation and behavior. The associated resources are blocked for the entire product lifetime.
Offline Environment
linkA setup where the machines do not have access to the internet.
Agent Node
linkA machine hosting the worker pods (the functional services). You can design a machine to be used as both a server and agent. Having separate server and agent nodes in a deployment is a topology design decision.
Server Node
linkA bare-metal or virtual machine hosting the cluster management server.
Application
linkSometimes referred to as an ArgoCD-managed application, an application is an ArgoCD object that wraps around a Helm chart. It normally denotes a Helm chart deployment. ArgoCD manages the applications delivered in Automation Suite. Example: ceph, orchestrator, platform.
Fabric
linkA collection of applications installed during the execution of the installer for the fabric stage. Examples: rancher-server, redis-cluster, fabric-installer.
Services Stage
linkA step in the installation process where service applications are installed.
ArgoCD
linkA 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 target state as specified in the docker registry.
UiPath® Product
linkSometimes referred to as a product, a UiPath® product is a collection of one or more applications that, together, provide a user-accessible service, for example, Orchestrator, Document Understanding, and others.
Services
linkA collection of applications installed during the execution of the installer for the services stage. Examples: platform, orchestrator, sfcore, uipath, webhook.