- Overview
- 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 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 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
- Support bundle log collection failure
- 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
- Pods cannot communicate with FQDN in a proxy environment
- 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
- Exploring Logs
Configuring an external Docker registry
Automation Suite can currently connect only with a Docker registry that is signed by a public certificate (for example, a public certificate provided by cloud providers such as ACR, ECR, etc.). We are still working on providing support for Docker registry signed by a private authority host.
You can opt for an external Docker registry only in new installations of Automation Suite. Migrating from the internal Docker registry to an external Docker registry is currently not supported.
OCI compliant registry - A registry implementation that meets the Open Container Initiative specifications. Formerly known as “Docker registry.” There are some widely used implementations, such as Azure Container Registry from Azure and Elastic Container Registry from AWS. In addition, there are self-hosted options such as the former container registry, now found under the Distributions repository.
Artifact - Under the OCI definitions, any image manifest or helm chart manifest hosted in an OCI compliant registry.
- Docker and Helm
as-images.txtas-helm-charts.txtmirror-registry.sh
Installing Docker and Helm
You must ensure that you have Docker and Helm installed on the machine from where you plan to upload the Automation Suite container images and Helm charts to your external Docker registry.
- To download the Docker binaries, see the official documentation.
- To download the Helm binaries, see the official documentation.
- To authenticate to the Docker registry, see the official documentation. Alternatively, you can use the following commands by replacing the sample credentials with your actual registry credentials:
docker login my.registry.io:443 --username "admin" --password "secret"docker login my.registry.io:443 --username "admin" --password "secret"
Downloading as-images.txt
as-images.txt, see Downloading installation bundles.
Downloading as-helm-charts.txt
as-helm-charts.txt, see Downloading installation bundles.
Downloading mirror-registry.sh
mirror-registry.sh script, see Downloading the installation packages.
mirror-registry.sh script requires outbound connectivity to the source (default registry.uipath.com) and target registries.
|
Command line argument |
Environment variable |
Description |
|---|---|---|
|
|
|
(Optional) Path to images manifest file. |
|
|
|
(Optional) Path to charts manifest file. |
|
|
|
(Mandatory) Pass the URL for the target registry. |
|
|
|
(Optional) pass the URL for the source registry; default to
registry.uipath.com.
|
# command line flags style
./mirror-registry.sh --target-registry-url my.registry.io:443 --source-registry-url registry.uipath.com --images-manifest /home/myuser/as-images.txt --helm-charts-manifest /home/myuser/as-helm-charts.txt# command line flags style
./mirror-registry.sh --target-registry-url my.registry.io:443 --source-registry-url registry.uipath.com --images-manifest /home/myuser/as-images.txt --helm-charts-manifest /home/myuser/as-helm-charts.txtThese steps are needed only if you use Computer Vision. You can perform these steps at any point in time before using the product.
To upload the optional Computer Vision images to your external Docker registry, take the following steps:
The following images are available for the Computer Vision Models:
aicenter/python36cv:v21.10.0-2aicenter/python36cvv3:23.4.0-rc19aicenter/cv2304:23.4.5.6
These steps are needed only if you use Document Understanding. You can perform these steps at any point in time before using the product.
To upload the optional Document Understanding images to your external Docker registry, take the steps in the Document Understanding documentation.
