- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions with cluster roles
- Granting installation permissions without cluster roles
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- 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 installation
- AI Trust Layer
- Troubleshooting
- 500 errors and rate limiting on S3 requests in ODF
- External Secrets troubleshooting
- Configuring CSI driver tolerations for ODF 4.20
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- Studio Desktop cannot load Integration Service connectors and activities
- TLS certificate validation errors
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Applying miscellaneous configurations
Create priority classes and namespace labels in Automation Suite on OpenShift when admin privileges are unavailable.
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>
The priority class name uipath-high-priority is required and cannot be changed.
Skipping the priority class
If you do not want to create a priority class, set ignore_priority_class to true in the input.json file. Automation Suite then omits priorityClassName from all workloads, so no PriorityClass needs to exist on the cluster and you can skip Creating a priority class.
If you are installing without cluster roles, you must set ignore_priority_class to true, because creating a cluster-scoped PriorityClass is not possible in that mode. For details, refer to Granting installation permissions without cluster roles.
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