- Overview
- Requirements
- Recommended: Deployment templates
- Manual: Preparing the installation
- Manual: Preparing the installation
- Step 1: Configuring the OCI-compliant registry for offline installations
- Step 2: Configuring the external objectstore
- Step 3: Configuring High Availability Add-on
- Step 4: Configuring Microsoft SQL Server
- Step 5: Configuring the load balancer
- Step 6: Configuring the DNS
- Step 7: Configuring the disks
- Step 8: Configuring kernel and OS level settings
- Step 9: Configuring the node ports
- Step 10: Applying miscellaneous settings
- Step 12: Validating and installing the required RPM packages
- Step 13: Generating cluster_config.json
- Cluster_config.json Sample
- General configuration
- Profile configuration
- Certificate configuration
- Database configuration
- External Objectstore configuration
- Pre-signed URL configuration
- ArgoCD configuration
- External OCI-compliant registry configuration
- Disaster recovery: Active/Passive and Active/Active configurations
- High Availability Add-on configuration
- Orchestrator-specific configuration
- Insights-specific configuration
- Process Mining-specific configuration
- Document Understanding-specific configuration
- Automation Suite Robots-specific configuration
- AI Center-specific configuration
- Monitoring configuration
- Optional: Configuring the proxy server
- Optional: Enabling resilience to zonal failures in a multi-node HA-ready production cluster
- Optional: Passing custom resolv.conf
- Optional: Increasing fault tolerance
- 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
- Step 15: Configuring the temporary Docker registry for offline installations
- Step 16: Validating the prerequisites for the installation
- Manual: Performing the installation
- Post-installation
- Cluster administration
- Managing products
- Getting Started with the Cluster Administration portal
- Migrating objectstore from persistent volume to raw disks
- Migrating from in-cluster to external High Availability Add-on
- Migrating data between objectstores
- Migrating in-cluster objectstore to external objectstore
- Migrating to an external OCI-compliant registry
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive or Active/Active deployment
- Guidelines on backing up and restoring an Active/Passive or Active/Active deployment
- Monitoring and alerting
- Migration and upgrade
- Migrating between Automation Suite clusters
- Upgrading Automation Suite
- Downloading the installation packages and getting all the files on the first server node
- Retrieving the latest applied configuration from the cluster
- Updating the cluster configuration
- Configuring the OCI-compliant registry for offline installations
- Executing the upgrade
- Performing post-upgrade operations
- Applying a patch
- 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 disable TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to expand AI Center storage
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- How to check the TLS version
- 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
- 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
- Support bundle log collection failure
- Single-node upgrade fails at the fabric stage
- Upgrade fails due to unhealthy Ceph
- RKE2 not getting started due to space issue
- Volume unable to mount and remains in attach/detach loop state
- Upgrade fails due to classic objects in the Orchestrator database
- Ceph cluster found in a degraded state after side-by-side upgrade
- Unhealthy Insights component causes the migration to fail
- Service upgrade fails for Apps
- In-place upgrade timeouts
- Docker registry migration stuck in PVC deletion stage
- AI Center provisioning failure after upgrading to 2023.10 or later
- Upgrade fails in offline environments
- SQL validation fails during upgrade
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- Setting a timeout interval for the management portals
- 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
- Update the underlying directory connections
- 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
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Pods stuck in Init:0/X
- Missing Ceph-rook metrics from monitoring dashboards
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- After Disaster Recovery Dapr is not working properly for Process Mining and Task Mining
- 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
- Automation Suite certificate is not trusted from the server where CData Sync is running
- Running the diagnostics tool
- Using the Automation Suite support bundle
- Exploring Logs
Step 16: Validating the prerequisites for the installation
uipathctl
installer to the /opt/UiPathAutomationSuite/<version>
folder on all the machines, generated the cluster_config.json
file, and copied the configuration file to all the machines. For instructions, see Downloading the installation packages and Generating cluster_config.json.
uipathctl
to evaluate your environment and generate a summary before performing the installation. You can use the --verbose
flag if you want to access the detailed prerequisites check output or you can skip this flag for a more concise and simplified
output.
The validation of prerequisites for installing Automation Suite involves two steps:
-
The first step uses
uipathctl
to evaluate the installation prerequisites for Kubernetes in your environment. -
The second step involves a detailed check of the prerequisites required by the shared components installation.
The following table lists all the prerequisite checks required for the Kubernetes installation.
Validation |
Description |
---|---|
Hardware requirements |
Validates that each machine in the cluster meets the hardware requirements. The check takes into account the following aspects:
|
Disk partitioning and configuration |
Validates that you properly partitioned and configured the disk. The check takes into account the following aspects:
|
SQL Server connectivity |
Validates the connectivity to the configured SQL Server and database. The check takes into account the following aspects:
|
Server certificate |
Checks that the server certificate you provided is valid. The check takes into account the following aspects:
|
Token-signing certificate |
Checks that the token-signing certificate you provided is valid. The check takes into account the following aspects:
|
Proxy |
Validates that you properly configure the proxy. The check takes into account the following aspects:
|
Connectivity |
Validates that all machines can connect to each other, that all the required URLs are on the firewall allowlist, and more. The check takes into account the following aspects:
|
System services |
Validates that system services are properly configured. The check takes into account the following aspects:
|
Software requirements |
Validates that all the required software is installed. If some software is not installed, the
install-uipath.sh installer attempts to install it.
|
Upgrade |
Validates if the upgrade path across Automation Suite versions is correct. |
In addition to the prerequisite checks required for the Kubernetes installation, the shared components installation requires specific prerequisite checks, as listed in the following table:
Check |
Description |
---|---|
SQL Connection |
Validates that Automation Suite can successfully connect to SQL server for UiPath® products and shared services (such as Identity,
Portal, Org Management, etc.) using the SQL connection strings provided in
cluster_config.json . This is mandatory for a successful installation.
|
SQL DB roles |
Validates the necessary roles and permissions required by UiPath® products. This is mandatory for a successful installation. |
SQL DB compatibility |
Validates SQL DB compatibility requirements. |
FQDN resolution |
Validates that the FQDN and the sub-domains are successfully resolvable. |
Object Storage API |
Validates that objectstore APIs are accessible based on access information provided in
cluster_config.json . This is mandatory for a successful installation of UiPath® Services.
|
Cache / Redis |
Validates the connection to Cloud Redis or ElastiCache. This is mandatory for a successful installation. |
Capacity |
Validates you have minimum worker nodes' CPU and RAM capacity based on products enabled in
cluster_config.json .
|
Storage Class |
Validates that the storage classes for File Storage are configured as required for Automation Suite Robots. |
Optional Components |
Validates that your cluster has components that you chose to exclude from the Automation Suite installation. |
Ingress |
Validates that the cluster ingress is configured correctly and the FQDN URL requests can reach UiPath® products. |
Network Policies |
Checks if network policies configured in Automation Suite are compatible with the cluster. |
Registry |
Validates that Automation Suite can access the UiPath® docker registry. This is mandatory for a successful installation. |
Cluster Connectivity |
Validates whether the cluster communication is configured properly:
|