- 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
- Setting up the required resources
- Prerequisite checks
- Output example: prerequisite check
- 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
Setting up the required resources
Use uipathctl prereq create to set up the databases, storage buckets, and other resources required for Automation Suite on OpenShift.
The uipathctl prereq create command generates the infrastructure and dependencies that Automation Suite requires, based on your input.json. If a resource already exists, the command leaves it unchanged, so you can run it safely more than once. Depending on your configuration, the command generates:
- The SQL databases required for the installation on the SQL server, if the
sql.create_dbkey is set totruein yourinput.jsonfile. This key auto-creates the databases. - The object storage buckets required for the installation, if the
external_object_storage.create_bucketkey is set totruein yourinput.jsonfile. This key auto-creates the buckets. - Additional required components, such as the External Secrets Operator, when the corresponding features are enabled (see the note below).
To generate them, run the following command:
uipathctl prereq create input.json --versions versions.json
uipathctl prereq create input.json --versions versions.json
For details on the flags that you can use with the uipathctl prereq create command, refer to uipathctl prereq create.
If you choose to enable a secretstore with Azure Key Vault, the External Secrets Operator and its corresponding Custom Resource Definitions (CRDs) will be deployed in the cluster as part of the prereq create command.
The uipathctl prereq create command does not create the required SQL databases for Process Mining. You must manually create them by following the instructions in Bring your own database.