- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- 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
- Troubleshooting
Automation Suite on OpenShift installation guide
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.
The Kubernetes cluster must have network connectivity and access to the secret store to retrieve credentials.
Automation Suite requires several infrastructure credentials to deploy all its products.
input.jsonuipathctl retrieves credentials from the configured secret store and applies them automatically.
You can store credentials such as:
- SQL credentials
- Username
- Password
- SQL Connection Strings
- Storage credentials
- S3/AWS
- Access key
- Secret key
- ARN (Amazon Resource Name)
- Azure
- Account key
- Client ID
- Client secret
- Subscription ID
- Tenant ID
- S3/AWS
- Redis credentials
- Password
- License
- Kerberos authentication
- AD username
- User keytab
- AD domain
- Ticket lifetime
Kubernetes Secret
input.jsonuipathctl uses the credentials stored in the Secret when deploying Automation Suite and its products.
Azure Key Vault
You can configure all sensitive data or credentials in an Azure Key Vault.
uipathctl uses the credentials stored in the Azure Key Vault when deploying Automation Suite.
