- 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
Glossary
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.
