- 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
Deployment scenarios
Automation Suite on OpenShift deployment
Deployment architecture
You can reference the following architecture diagrams to deploy Automation Suite on OpenShift.
Overview
The OpenShift architecture comprises the control plane nodes and the compute nodes. The control plane nodes host the control plane applications of Kubernetes, such as API servers, etcd, schedulers, etc., whereas the compute nodes host other applications like the monitoring stack, networking, etc. Automation Suite is also installed on the compute nodes.
Automation Suite relies on Istio for networking and ArgoCD for deployment. You can replace Istio with the OpenShift Service Mesh and ArgoCD with the OpenShift GitOps Operator.
The following components are also required:
- Redis
- An S3-compatible objectstore
- Microsoft SQL Server
- Block storage
You can meet the Redis requirement by using the Redis Enterprise Operator from OpenShift or installing High Availability Add-on on separate machines.
You can use OpenShift Data Foundation for the S3 Objectstore buckets and the block storage.