automation-suite
2024.10
false
- 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
Last updated Mar 26, 2026
Applying miscellaneous configurations
Note:
Only apply the configurations in this section if you cannot provide admin privileges to the Automation Suite installer. If you can provide the required permissions to the installer, you do not need to apply the configurations in this section.
Creating a priority class
To create a priority class for UiPath® applications, take the following steps:
- Save the following configuration as a YAML file:
--- apiVersion: scheduling.k8s.io/v1 kind: PriorityClass metadata: name: uipath-high-priority value: 1000000 preemptionPolicy: PreemptLowerPriority globalDefault: false description: "Priority class for uipath applications"--- apiVersion: scheduling.k8s.io/v1 kind: PriorityClass metadata: name: uipath-high-priority value: 1000000 preemptionPolicy: PreemptLowerPriority globalDefault: false description: "Priority class for uipath applications" - Run the following command, replacing the
<file_name.yaml>placeholder with the actual name of your YAML file:oc apply -f <file_name.yaml>oc apply -f <file_name.yaml>
Labeling the namespaces
To create namespace labels, run the following commands:
oc label namespace <uipath> uipath-injection=enabled
oc label namespace <uipath> istio-injection=enabled
oc label namespace <uipath> uipath-injection=enabled
oc label namespace <uipath> istio-injection=enabled