- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- Troubleshooting

Automation Suite on OpenShift installation guide
Upgrading Automation Suite
Automation Suite consists of multiple components. Both you as a customer and UiPath® share responsibility of these components. For details, see Responsibility matrix.
You are responsible for upgrading:
- Kubernetes infrastructure where Automation Suite is deployed (OpenShift)
- Components that you choose to bring as part of Automation Suite (e.g., Gatekeeper, FluentD, etc.)
UiPath® is responsible for upgrading:
- UiPath® services (e.g., Orchestrator)
- Components deployed as part of Automation Suite (e.g., ArgoCD)
Upgrading UiPath® services and components
Preparation
If you upgrade to Automation Suite 2024.10.3 or higher, and you want latest version of Airflow you need to bring a PostgreSQL database for AutomationSuite_Airflow and configure the connection string for it in input.json.
Refer to Process Mining-specific configuration for details.
To prepare for the upgrade, take the following steps:
- Check the compatibility matrix to determine the supported versions for each available upgrade scenario. If you brought your own components, make sure the versions of your components are compatible with the version you plan to upgrade to. For details, see Compatibility matrix.
- Download
versions.jsonanduipathctlfor the version you want to upgrade to, on your management machine. For download instructions, see Downloading the installation packages. - Generate the latest
input.jsonfile as follows:- Option A: To get the latest revision of your
input.jsonfile, run the following command:uipathctl manifest get-revisionuipathctl manifest get-revision - Option B: To list all the past
input.jsonfiles and determine the one you want to choose, run the following command:uipathctl manifest list-revisionsuipathctl manifest list-revisions
- Option A: To get the latest revision of your
- If you are using an offline setup with an external OCI-compliant registry, you must hydrate the registry with container images and Helm charts before upgrade. For details, refer to Hydrating the registry with the offline bundle.
- If Process Mining is installed, and you want to use latest version of Airflow which needs PostgreSQL, you must add or update the
sqlalchemyconnection string template applicable for PostgreSQL in thecluster_config.jsonfile before the upgrade:postgresql_connection_string_template_sqlalchemy_pyodbc.postgresql+psycopg2://<user>:<password>@<postgresql host>:<postgresql port>/<airflow db name>postgresql+psycopg2://<user>:<password>@<postgresql host>:<postgresql port>/<airflow db name>Note:This only applies to Process Mining on Automation Suite 2024.10.3 or higher.
Execution
To perform an upgrade of UiPath® services and component, take the following steps:
- Confirm that your cluster is healthy:
uipathctl health check --namespace <uipath> --versions versions.jsonuipathctl health check --namespace <uipath> --versions versions.json - Put the cluster in maintenance mode to guarantee a consistent backup:
uipathctl cluster maintenance enableuipathctl cluster maintenance enableImportant:This operation causes downtime, and your business automation is suspended while maintenance mode is enabled.
- Verify that the cluster is in maintenance mode:
uipathctl cluster maintenance is-enableduipathctl cluster maintenance is-enabled - Back up the cluster and the SQL database, then check that the backup completed successfully.
Important:
It is strongly recommended to create a backup of the cluster and the SQL database before upgrading Automation Suite. This is to ensure you can restore the cluster if something goes wrong during the upgrade operation. This is applicable before upgrading your Kubernetes infrastructure as well. Make sure to copy the value of
global.userInputs.identity.krb5KeytabSecrettoglobal.kerberosAuthConfig.userKeytab, if you simultaneously meet the following requirements:- you configured the Active Directory integration using username and password
- you have Windows authentication enabled
- you do not use SQL integrated authentication
- Disable the maintenance mode:
uipathctl cluster maintenance disableuipathctl cluster maintenance disableNote:You must disable maintenance mode before upgrade. The Automation Suite upgrade process does not support having maintenance mode enabled.
- Perform the upgrade of UiPath® services and components:
uipathctl cluster upgrade input.json --versions versions.jsonuipathctl cluster upgrade input.json --versions versions.jsonImportant:This operation causes downtime, and your business automation is suspended during the upgrade process. It is important that you perform the upgrade only during your maintenance window.
- Check that the cluster is healthy after the upgrade:
uipathctl health check --namespace <uipath> --versions versions.jsonuipathctl health check --namespace <uipath> --versions versions.jsonNote:If you upgraded to Automation Suite 2024.10.3 or higher, you can uninstall Dapr and Cert Manager if you have not enabled Task Mining. For more details, refer to the Uninstall Dapr and Uninstall Cert Manager sections.
Upgrading Kubernetes infrastructure
Automation Suite supports upstream N-1 to N-3 versions of Kubernetes irrespective of the cloud provider. For instance, if upstream is 1.27, we support versions 1.26, 1.25, and 1.24. For supported versions, see the Compatibility matrix.
You are responsible for upgrading the Kubernetes infrastructure hosting Automation Suite. You should follow the standard practices of your company to upgrade Kubernetes infrastructure.