- Overview
 - Requirements
 - Installation
- Q&A: Deployment templates
 - Downloading the installation packages
 - Install-uipath.sh Parameters
 - Enabling Redis High Availability Add-On for the cluster
 - Document Understanding configuration file
 - Adding a dedicated agent node with GPU support
 - Connecting Task Mining application
 - Adding a dedicated agent Node for Task Mining
 - Adding a Dedicated Agent Node for Automation Suite Robots
 
 - Post-installation
 - Cluster administration
 - Monitoring and alerting
 - Migration and upgrade
- Migration options
 - Step 1: Moving the Identity organization data from standalone to Automation Suite
 - Step 2: Restoring the standalone product database
 - Step 3: Backing up the platform database in Automation Suite
 - Step 4: Merging organizations in Automation Suite
 - Step 5: Updating the migrated product connection strings
 - Step 6: Migrating standalone Insights
 - Step 7: Deleting the default tenant
 
- Performing a single tenant migration
 
 - 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 clear Redis data
 - 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 disable streaming logs for AI Center
 - How to debug failed Automation Suite installations
 - How to delete images from the old installer after upgrade
 - How to automatically clean up Longhorn snapshots
 - How to disable TX checksum offloading
 - How to address weak ciphers in TLS 1.2
 
- 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
 - First installation fails during Longhorn setup
 - SQL connection string validation error
 - Prerequisite check for selinux iscsid module fails
 - Azure disk not marked as SSD
 - Failure after certificate update
 - Antivirus causes installation issues
 - Automation Suite not working after OS upgrade
 - Automation Suite requires backlog_wait_time to be set to 0
 - Volume unable to mount due to not being ready for workloads
 - Unable to launch Automation Hub and Apps with proxy setup
 
- Failure to upload or download data in objectstore
 - PVC resize does not heal Ceph
 - Failure to resize PVC
 - Failure to resize objectstore PVC
 - Rook Ceph or Looker pod stuck in Init state
 - StatefulSet volume attachment error
 - Failure to create persistent volumes
 - Storage reclamation patch
 - Backup failed due to TooManySnapshots error
 - All Longhorn replicas are faulted
 
- Setting a timeout interval for the management portals
 - Update the underlying directory connections
 - Authentication not working after migration
 - 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 due to invalid status code
 - Alarm received for failed Kerberos-tgt-update job
 - SSPI provider: Server not found in Kerberos database
 - Login failed for AD user due to disabled account
 - ArgoCD login failed
 
- 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
 - MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
 - MongoDB Pod Fails to Upgrade From 4.4.4-ent to 5.0.7-ent
 - Unhealthy services after cluster restore or rollback
 - Pods stuck in Init:0/X
 - Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
 - Missing Ceph-rook metrics from monitoring dashboards
 - Pods cannot communicate with FQDN in a proxy environment
 
- Using the Automation Suite Diagnostics Tool
 - Using the Automation Suite support bundle
 - Exploring Logs
 
 

Automation Suite installation guide
A 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.
A relationship between two ArgoCD applications, where one requires the other in order to function.
The machine resources (CPU, memory) a product needs for an optimal installation and behavior. The associated resources are blocked for the entire product lifetime.
A 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.
Sometimes 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.
A collection of applications installed during the execution of the installer for the fabric stage. Examples: rancher-server, redis-cluster, fabric-installer.
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 target state as specified in the docker registry.
Sometimes 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.