- 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
- B) 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 bundle
- 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 NIC 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
- 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
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Configuring the load balancer
A load balancer is mandatory for the multi-node HA-ready production setup.
Automation Suite supports two types of configuration for the load balancer, as shown in the following sections.
You can configure the load balancer to use session persistence or sticky sessions, but it is not a requirement.
Currently, Automation Suite supports only a Layer 4 (network layer) load balancer.
The load balancer does not support TLS encryption and termination. For effective service operation, make sure to configure your load balancer to facilitate traffic pass-through.
This is the recommended configuration for the load balancer.
You need to create two backend pools that meet the following requirements:
-
Server Pool
- Consists of all the server nodes.
- There must not be any agent nodes in the Server Pool.
-
Node Pool
-
Consists of all the server nodes and non-specialized agent nodes. Specialized agent nodes include
task-mining
,gpu
,asrobots
.
-
Probe |
Protocol |
Port |
Interval |
Re-entry threshold |
Associate pool |
---|---|---|---|---|---|
|
TCP |
|
15 sec |
2 |
Node Pool |
|
TCP |
|
15 sec |
2 |
Server Pool |
Refer to the following illustration for more details on the configuration
Ensure you have the following ports enabled on your firewall for the source of load balancer:
Port |
Protocol |
Purpose |
Traffic forwarding |
Health probe |
---|---|---|---|---|
|
TCP |
For HTTPS (accessing Automation Suite) |
Traffic on this port should be forwarded to Node Pool. |
|
|
TCP |
For accessing Kube API using HTTPS; required for node joining. |
Traffic on this port should be forwarded to Server Pool. |
|
|
TCP |
For accessing Kube API using HTTPS; required for node joining. |
Traffic on this port should be forwarded to Server Pool. |
|
For any ports other than HTTPS, we recommend it is not exposed outside the cluster. Run your nodes behind a firewall / security group.
If you have a firewall setup in the network, make sure that it has these ports open to allow traffic from those ports.
Refer to the following illustration for more details on the configuration.
This configuration does not have resilience to nodes going down during installation.
If the primary server is down or deleted, cluster configuration needs to be updated.
FQDN of the primary server needs to be remapped to a different machine in the cluster that is available.
Ensure that you have the following ports enabled on your firewall for the source of load balancer:
Port |
Protocol |
Purpose |
Traffic forwarding |
---|---|---|---|
|
TCP |
For HTTPS (accessing Automation Suite). |
Traffic on this port should be forwarded to the Node Pool. |