automation-suite
2023.4
false
- Overview
- Requirements
- Root privileges requirements
- High Availability – three availability zones
- Certificate requirements
- Network requirements
- Installation
- Q&A: Deployment templates
- Configuring the machines
- Configuring the external objectstore
- Configuring an external Docker registry
- Configuring the load balancer
- Configuring the DNS
- Configuring Microsoft SQL Server
- Configuring the certificates
- Online multi-node HA-ready production installation
- Offline multi-node HA-ready production installation
- Disaster recovery - Installing the secondary cluster
- 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
- Adding a dedicated agent Node for Task Mining
- Connecting Task Mining application
- 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 TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to generate the encoded pull_secret_value for external registries
- 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
- GPU node affected by resource unavailability
- Volume unable to mount due to not being ready for workloads
- 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
- Issues accessing the ArgoCD read-only account
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- 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
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- Unable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string
- Airflow installation fails with sqlalchemy.exc.ArgumentError: Could not parse rfc1738 URL from string ''
- How to add an IP table rule to use SQL Server port 1433
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Automation Suite on Linux Installation Guide
Last updated Oct 4, 2024
High Availability – three availability zones
Kubernetes is designed to run a single cluster across multiple availability zones. To ensure resiliency against a zone failure,
you can deploy critical components, including
kubernetes and uipath product services, in High Availability (HA) mode.
HA mode requires at least three server nodes deployed in three distinct availability zones.
Note: Availability zones can be generalized as data centers. Clusters spanned across multiple data centers are more highly available
than all availability zones in the same data centers.
To ensure HA with three availability zones, the following requirements must be met:
- Three availability zones that are geographically separate but within close proximity;
- Round Trip Time (RTT) among the availability zones must be minimal (<10 ms RTT);
- All availability zones must provide a consistent set of resources with HA and redundancy;
- Single virtual network span across all the availability zones.
Note:
High Availability Add-On (HAA) is required for deploying Orchestrator in a three active availability zone topology on Automation Suite.
The architecture of a configuration with HA with three availability zones has the following characteristics:
- All three zones are linked in the same virtual network;
- Each of the zones must host at least one server node so that there are at least three server nodes installed in Automation Suite to maintain the quorum requirement;
- Each of the zones should host additional balanced
number of agent nodes to meet the overall hardware requirements for running
Automation Suite.
Note:
- SQL server must be configured as failover group spanning across two zones to ensure the entire deployment is resilient to the failure of one zone.
- A minimum of three nodes are required for Elasticsearch in any of the two zones, configured in different clusters and synchronized.
- A minimum of two load balancers in any of the two zones, to ensure High Availability at load balancer level.
To ensure both HA and Disaster Recovery, you can employ the deployment model illustrated in the following image. In this example, all three zones are active, and the traffic manager is employed to use a specific algorithm, such as Round Robin or one of its variants to direct traffic to any of the load balancers. Similarly to the traffic manager, the load balancer will direct traffic to any of the availability zones.
