- Overview
- Glossary
- Automation Suite Products
- Cross-product Dependencies
- Supported use cases for single-node and multi-node installations
- Cross-deployment Feature Comparison
- Certificates 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
Supported use cases for single-node and multi-node installations
Why the single-node mode is only suitable for evaluation purposes, whereas the multi-node profile can be implemented in production.
Automation Suite supports two deployment modes, each targeted at specific use cases, as explained in the following table:
Deployment mode |
Description |
---|---|
Single-node — evaluation |
Supported only for evaluation and demo scenarios. |
Multi-node — production, HA-enabled |
The only configuration supported for production deployments. You can perform additional configuration post-deployment to have full HA capabilities. |
Automation Suite uses a cloud native architecture based on Kubernetes. It provides all the benefits in scale, automatic resource management, and reliability that come with Kubernetes.
To offer these benefits, the Kubernetes design is based on the following fundamental aspects:
- Running on an uneven number of multiple machines (3, 5, 7, etc.);
- Using the quorum principle to handle independent node failures and data corruption. For a cluster of N machines, as long as there is still a number of N/2 + 1 machines that have quorum, the cluster is functional and can recover gracefully with no observed failures.
By definition, single-node deployments do not benefit from the previously described characteristics and are not supported for production deployments. Failures and data loss can and will occur. In case of failure, data recovery for single-node deployments without backup is not supported.
However, since support for single-node deployments is valuable for evaluation and demo scenarios, UiPath® offers this deployment option applicable to some specific use cases.